On Wed, May 28, 2014 at 16:57:28 +0200, Nils Gladitz wrote:
> I assumed that because people kept removing the soname options for their
> Android toolchains that SONAMEs aren't supported at all.
No idea.
> It however looks like they just can't have versioned names.
> Perhaps ignoring the VERSION/SOVERSION properties would suffice since
> the default SONAME should work which would make this topic superfluous
> at least for android.
> It sounds like you probably already have all of that covered.
Here's the commit which added it to my working branch:
https://github.com/mathstuf/CMake/commit/d4a2a23b9d500434e294ad2b8515731aeaee7c30
For the lazy, the commit message:
Android: Support sonames on Android
This is actually required because without it, the APK will be
bundle up any library linking to a library without a SONAME with an
absolute path.
I don't know about SOVERSION; the project I'm using it with[1] isn't
using it.
--Ben
[1]https://github.com/mathstuf/abagames-gunroar
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
