AndroidApp—适配arm64v8a的探索

        目前&＃xff0c;华为、小米、三星、OPPO、VIVO等应用商店已经支持32位和64位APP&＃xff0c;Google Play已经强制要求上传64位的APP&＃xff0c;而且Google明确了在Android 12上只支持64位的APP&＃xff0c;32位App将会被抛弃。

        随着手机CPU采用arm64-v8a架构达到了90%以上&＃xff0c;剩余的基本是32位架构的armeabi-v7a&＃xff0c;而armeabi、x86、x86_64基本已经没有在使用的真实设备。虽然我们依旧可以在arm64-v8a架构的设备上运行只适配了32位armeabi-v7a架构的APP&＃xff0c;但是适配了64位的APP有内存使用率、性能体验等方面的优势&＃xff0c;所以APP针对arm64-v8a架构的64位适配势在必行。

        分析APP启动过程发现&＃xff0c;64适配重点就是so库的适配&＃xff0c;这里先不讨论so动态下发、应用内更新、以及具体的踩坑过程。由于无论是自己编译生成so库&＃xff0c;还是第三方直接提供so库&＃xff0c;最后都能得到相应架构的so库&＃xff0c;所以这里主要讲述下&＃xff1a;如何做工程改造、以及如何做链路改造。

方案一&＃xff1a;ABI Filters

        在 gradle.properties 文件中&＃xff0c;配置 COMPLIE_32_BIT_VERSION 变量&＃xff1a;

#编译的APK是否为32位
COMPLIE_32_BIT_VERSION &＃61; true

        在app模块的 build.gradle 文件里&＃xff0c; 读取 COMPLIE_32_BIT_VERSION 变量&＃xff0c;来确定需要包含哪些架构的so库&＃xff1a;

android {...defaultConfig {...ndk {def filters &＃61; "arm64-v8a"boolean compile32Bit &＃61; Boolean.valueOf(COMPILE_32_BIT_VERSION)if (compile32Bit) {filters &＃61; "armeabi-v7a"}abiFilters filters}}packagingOptions {// 剔除打包了无用so库的问题exclude &＃39;lib/x86/xxx.so&＃39;exclude &＃39;lib/x86_64/xxx.so&＃39;// 解决so库重复打包的问题pickFirst &＃39;lib/armeabi-v7a/xxx.so&＃39;pickFirst &＃39;lib/arm64-v8a/xxx.so&＃39;}...
}


        在Jenkins参数化构建时&＃xff0c;替换掉 COMPLIE_32_BIT_VERSION 变量的值&＃xff0c;来生成期望架构的APK&＃xff1a;

结果如下&＃xff1a;

方案二&＃xff1a;APK Split

        在app模块的 build.gradle 文件里&＃xff0c;做类似以下的配置&＃xff0c;会自动生成多个APK文件。其可通过屏幕密度&＃xff08;mdpi, hdpi, xhdpi…&＃xff09;或者处理器架构(arm64-v8a, armeabi-v7a…)来进行拆分&＃xff0c;还可以生成是否包含多种架构的通版APK。

android {...defaultConfig {...splits {// Configures multiple APKs based on ABI.abi {def isReleaseBuild &＃61; falsegradle.startParameter.taskNames.find {// Enable split for release builds in different build flavors// (assemblePaidRelease, assembleFreeRelease, etc.).if (it &＃61;&＃61;~ /:app:assemble.*Release/) {isReleaseBuild &＃61; true// breakreturn true}// continuereturn false}// Enables building multiple APKs per ABI.enable isReleaseBuild// By default all ABIs are included, so use reset() and include to specify that we only// want APKs for x86, armeabi-v7a, and mips.reset()// Specifies a list of ABIs that Gradle should create APKs for.include "armeabi-v7a", "arm64-v8a", "x86_64"// Specifies that we want to also generate a universal APK that includes all ABIs.universalApk true}}}...
}

        除了生成像方案一中arm64-v8a、armeabi-v7a架构的APK&＃xff0c;还生成了只包含x86架构和所有架构的通版APK&＃xff1a;

方案三&＃xff1a;APK Split &＃43; ABI Filters

        在开发中发现&＃xff0c;方案二不支持Android Studio直接install APK到设备上运行。为了方便调试&＃xff0c;debug包依然采用ABI Filters包含多种架构的方式&＃xff1a;

android {...defaultConfig {...splits {abi {def isDebugBuild &＃61; falsegradle.startParameter.taskNames.find {if (it.toLowerCase().contains("debug")) {isDebugBuild &＃61; true}}if (!isDebugBuild) {enable truereset()universalApk false} else {// AS直接run到设备上ndk {abiFilters "armeabi-v7a", &＃39;arm64-v8a&＃39;, &＃39;x86-64&＃39;}}}}}...
}

参考&＃xff1a;

https://developer.android.com/google/play/publishing/multiple-apks

https://blog.csdn.net/weixin_38753262/article/details/107873316

https://mp.weixin.qq.com/s/SHFqS3RKKlprijlf6hL09w

https://blog.csdn.net/wangqjpp/article/details/107115599

https://www.jianshu.com/p/76db8b87fac3

https://www.jianshu.com/p/a5314382b64c