![]() That's the purpose of the fat binary - the system automatically loads the library appropriate for the target architecture. There shouldn't be any need to conditionally compile in the code for each target device. Android C/C developer kit Android NDK Open Handset Alliances Android NDK (Native Dev Kit) The Android NDK is a toolset that lets you implement parts. With Android NDK r10 and later, the Intel® C Compiler for Android (ICC) is no longer the default compiler in the NDK build system after Intel INDE is installed. Because it is compiled on the Android platform, it is best to use the cross tool chain provided by ndk, for example, I used linaro 4.9 As a result. When you run your fat binary containing both 32 and 64-bit code on a 32-bit system, it will load the 32-bit code and vice versa. Then, in your Android.mk file, you can add specific settings for each CPU type: ifeq ($(TARGET_ARCH_ABI),armeabi-v7a) For example, to build a FAT binary containing both ARMv7a and ARMv8 code, add the following line to your Application.mk file: APP_ABI := arm64-v8a armeabi-v7a Android allows you to bind native code libraries with multiple ABI's (CPU-specific code) into an APK. ![]() Is it possible that I can compile the same project first using 32 bit (commenting 64 architectures) and compile using 64 bit(uncomment 64 architectures) and run on both.Ħ4-bit ARM
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |