[Development] Android missing SONAME in lib's causes

Simon Lees simon.lees at codan.com.au
Fri Jul 12 03:54:07 CEST 2013

On 07/11/2013 10:11 PM, Rafael Roquetto wrote:
> On Thu, Jul 11, 2013 at 09:14:39AM -0300, Rafael Roquetto wrote:
>> On Thu, Jul 11, 2013 at 10:31:30AM +0930, Simon Lees wrote:
>>> Hi,
>>> I have tried adding
>>> and alternatively
>>> To both my CMakeLists.txt and the toolchain file (One at a time) Neither
>>> have helped, is this what you meant? If it is can you send me a copy of
>>> your config files so i can look for differences. I am using the android
>>> toolchain file from the same location as Stephen.
>> You can take a look at /usr/share/cmake-2.8/Modules/Platform/QNX.cmake for
>> instance, to see whatis being passed to the QNX compiler. It may be that your
>> problem has a different cause. One thing you could do is try to build the
>> library manually, replicating the compiler/linker line cmake uses, and tweak
>> it to see if this is really the compiler that is not adding SONAME to the
>> libs. Just an idea.
> Sorry, I seem to have misunderstood the issue. I thought the problem was that
> some libs that were being built against Qt libs were not carrying SONAME, not
> Qt binaries themselves. If Qt binaries aren't carrying SONAME, then it has
> nothing to do with CMake, but with the way Qt for Android is being built. I
> still think either the wrong flags are being passed to the compiler driver or
> that it has to do with your Android toolchain configuration. Check how Qt is
> being built, what's being passed to the compilers, the android mkspecs, etc...
> Rafael
I had a play with the android mkspecs the other day, but didn't get 
anywhere. This is probably due to my very limited understanding of the 
Qt build system, i'll have another play today if anyone has suggestions 
i'd love to here them, i'm also sitting around on irc as Simotek-Work



More information about the Development mailing list