Android notes: About so files

The project contains a number of third-party libraries with so files, with different supported platforms. When the app crashes on the 5.0 system, it is discovered that some third-party libraries of x86-64 so files are not installed.

Look at the official website of the Abimanager, it seems to write not clear enough. During the process, it was found that a note accompanying the Carrier Pigeon SDK was an easy way to understand the installation mechanism of so files.

1. So supports all Android platforms, but the Libs directory is only available for the Armeabi platform, so the other platforms can be found in the all-platform-so of the upper directory, given that the usual access is generally only required for the platforms. So. 2. Possible problems embedding. So: The a.so file does not match the jar package. WORKAROUND: Update the corresponding so file while updating the jar; b. The current project already has some platform so, such as only the Armeabi platform, but added carrier pigeon all platforms caused by the package exception. Workaround: Add only the pigeons so file that is currently in the project's existing platform. Refer to the online or the following example: Armeabi! This platform has existing so and homing pigeon, normal! --libcurrent.so current project has so--libtpnssecurity.so carrier pigeon--libtpnswatchdog.so homing pigeon armeabi-v7a! This platform has existing so and homing pigeon, normal! --libcurrent.so current project has so--libtpnssecurity.so carrier pigeon--libtpnswatchdog.so homing pigeon mips!!! Error, because this platform only homing pigeon, must delete the MIPS directory!!! --libtpnssecurity.so homing pigeon--libtpnswatchdog.so homing pigeon x86!!! Error, because this platform only homing pigeon, must delete the x86 directory!!! --libtpnssecurity.so homing Pigeon--libtpnswatchdog.so pigeon C. If no so file exists for the current project. WORKAROUND: Copy all carrier pigeon platforms or just copy the Armeabi platform

Combined with other reference articles, you should probably summarize the following:

1. Contains at least Armeabi platform

2. Many different libraries have so files that are based on the one that contains the least supported platforms
   

Other references:

1.http://www.open-open.com/lib/view/open1440421271716.html

2.http://stackoverflow.com/questions/30782848/how-to-use-32-bit-native-libaries-on-64-bit-android-device

This article from the "Sky no traces but I flew" blog, please be sure to keep this source http://glblong.blog.51cto.com/3058613/1698839

Android notes: About so files