Supported CPU Architectures
PSPDFKit includes native libraries for the following Android ABIs:
32-bit ARMv7 (
64-bit ARMv8 (
32-bit x86 (
64-bit x86 (
This ensures the best optimization and performance on most Android devices currently sold. When your app is installed on a device, the appropriate native binary is unpacked from the APK and used.
If your app contains any other native libraries, you’ll have to make sure you only have
x86-64 versions of them as well. That is due to Android demanding that all loaded native libraries be built for the same architecture. For example, if the first native library loaded is
armeabi-v7a, Android will only look for
armeabi-v7a libraries on all
System.loadLibrary() calls after that. If it doesn’t find that exact architecture, it’ll throw the
ARMv8 devices can load and run both
armeabi-v7a binaries. x86 devices can load and run
armeabi-v7a binaries via the
libhoudini layer. This means that if you’re really pressed for binary size, you can ship only
armeabi-v7a native libraries and your application will still work on ARMv7, ARMv8, x86, and x86-64 devices.
This will come at a cost of general performance — you can expect about a 20-30 percent performance hit when rendering on modern ARMv8 devices, and a more severe 30-60 percent hit on x86 devices.
For more information, please read about stripping away architectures.
Since every architecture shipped adds about 5–10 MB to a final application’s APK, we’re shipping the bare minimum for best performance.
armeabi— ARMv5/6 are old architectures that haven’t been used in years, since Android 2.3, and due to limitations of architecture, PSPDFKit rendering was just too slow to be usable. This is why we don’t ship this architecture at all. All new devices (Android 4.0 or newer) support at least ARMv7 architecture with NEON. Support for
armeabiwas removed within the NDK 17.
mips64— MIPS is exclusively used for some rare embedded uses of Android. There has been no Android phone or tablet with a MIPS core released in general market.