|| at May 14, 2012 at 6:32 am
On Mon, May 14, 2012 at 12:48 AM, Wil Hadden wrote: On Tuesday, 1 May 2012 20:20:53 UTC+1, Chris Stratton wrote:
On May 1, 11:33 am, Wil Hadden wrote:
I can happily create builds for arm7, arm5 and presumably x86 but
could someone explain or point me to a description of how to create a
fat binary using a standalone toolchain?
AFAIK 'fat binary' is a bit of misnomer on Android - the normal ndk
toolchain creates one distinct .so per ABI listed in the Android.mk,
and copies them all to where the packager will combine them in a
single APK so that the device can install whichever is appropriate.
The only thing that is really "fat" is the apk.
Sorry to resurrect this but I am doing something wrong!
I should say that I am using a standalone toolchain so I need to do
everything manually. I can create separate so files for every platform I
want to support, and obviously I can copy them to libs so they get picked
up by the packager. My problem is that when I go to load them with
System.loadLibrary I need to supply a specific library name.
Can anyone tell me what I am doing wrong?
All libraries should have the same name, but be placed in different
ABI-specific directories, as in:
The PackageManager will pick up the best library for your device at install
time (from the .apk) and copy it to $DATA_DIR/lib/libfoo.so
All you need to do in Java is System.loadLibrary("foo")
For more details on how this works, read $NDK/docs/CPU-ARCH-ABIS.html, it
has a section named "CPU ABI Management on the Android platform".
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to email@example.com.
For more options, visit this group at http://groups.google.com/group/android-ndk?hl=en.