armeabi and armeabi-v7a folder

android arm android-ndk eabi
codereviewanskquestions picture codereviewanskquestions · Jun 6, 2011 · Viewed 23.5k times · Source

I'm working on an Android project and I am using the NDK to call native methods. I have two libraries (.so files) and one is located in the libs/armeabi folder and the other one is located in the libs/armeabi-v7a lib folder.

If I try to run the application then it won't load the library in the /libs/armeabi folder. If I move the library file to the libs/armeabi-v7a folder, then it loads the library but after 5 to 10 minutes it crashes and gives a segmentation fault error.

I was wondering if the location of the library (different folder) might cause this problem.

Answer

loveisbug picture loveisbug · Apr 25, 2013

When installing an application, the package manager service will scan the .apk and look for any shared library of the form:

     lib/<primary-abi>/lib<name>.so

If one is found, then it is copied under $APPDIR/lib/lib.so, where $APPDIR corresponds to the application's specific data directory.

If none is found, and a secondary ABI is defined, the service will then scan for shared libraries of the form:

    lib/<secondary-abi>/lib<name>.so

If anything is found, then it is copied under $APPDIR/lib/lib.so.

For the primary/secondary abi,

The Android system knows at runtime which ABI(s) it supports. More precisely, up to two build-specific system properties are used to indicate:

  • the 'primary' ABI for the device, corresponding to the machine code used in the system image itself.

  • an optional 'secondary' ABI, corresponding to another ABI that is also supported by the system image.

For example, a typical ARMv5TE-based device would only define the primary ABI as 'armeabi' and not define a secondary one.

On the other hand, a typical ARMv7-based device would define the primary ABI to 'armeabi-v7a' and the secondary one to 'armeabi' since it can run application native binaries generated for both of them.

This mechanism ensures that the best machine code for the target device is automatically extracted from the package at installation time.

Related questions

Why use armeabi-v7a code over armeabi code?

In my current project I make use of multiple .so files. These are located at the armeabi and armeabi-v7a folder. Unfortunately one of the .so files is a 6MB and I need to reduce file size. Instead of having …

Read More
Cross compiling static C hello world for Android using arm-linux-gnueabi-gcc

I want to build a static hello world from C using arm-linux-gnueabi-gcc as opposed to using the NDK standalone toolchain or Codesourcery for that matter. In Ubuntu... I have done the following: sudo apt-get install gcc-arm-linux-gnueabi I created a hi.…

Read More
Want to compile native Android binary I can run in terminal on the phone

I've been trying for a couple days to compile a native ARM Android binary that will execute on my phone using a terminal application. I want to generate the same type of binary as the standard Posix binaries installed on …

Read More