So I thought I could now upload my app using different NDK compiled libraries for targeted CPU architectures but it seems like that\'s not possible.
Anyone know how to u
Well, finally Google Play allows to have Multi-apk targeting!
"We have added new functionality for apps that use multiple APK support. You can now target each APK to a specific native platform."
Please see Multiple APK Support in the Android documentation. This details some of the specifics of releasing multiple APKs of the same product/application.
As for the NDK specifics, and as already mentioned, you can utilize multiple platforms / ABIs in the APP_ABI value of your Android.mk.
In new Play store developer console if you want to add multiple APK than you must need to use same package name and same keystore key but different version code. You have publish app then first upload Apk e.g mobile_release and rollout for production, after when you upload another apk, you should choose option RETAIN on previous APK also with current APK.
android {
// To create different apk per abi
splits {
abi {
enable true
reset()
include 'armeabi', 'armeabi-v7a', 'x86'
universalApk true
}
}
}
import com.android.build.OutputFile
// Map for the version code
ext.versionCodes = ['armeabi': 1, 'armeabi-v7a': 2, 'x86': 3]
android.applicationVariants.all { variant ->
// assign different version code for each output
variant.outputs.each { output ->
int abiVersionCode = project.ext.versionCodes.get(output.getFilter(OutputFile.ABI)) ?: 0
output.versionCodeOverride = (abiVersionCode * 1000) + android.defaultConfig.versionCode
}
}
You can declare supports-gl-texture in your AndroidManifest.xml
for each separately compiled (and re-packaged) app. This will provide Market filtering, so a single user will only see one version of your app.
Unless you have a bunch of code for your app, I would suggest just putting the native code for the three architectures that android supports and the moment, armv5, armv7, and x86. It willl triple the size of the code portion of your apk, but 3*(a small number) is still a small number. You can do this by modifying your jni/Application.mk file, or creating it if you don't already have it, and add the line:
APP_ABI := armeabi armeabi-v7a x86
This will compile for all three.
Note though that there's a bug with the current ndk (ndk r6), that tries to link the x86 code to the arm code. This is fixed if you get the AOSP project, source.android.com, or you can just wait until google releases r6b, which will likely have the fix. Otherwise, if you you don't want to do that, you can just leave off the x86 portion of the line for now, and release your app without x86 code in it, and push an update when the new ndk comes out. I'm not aware of many popular devices that use x86 instructions yet.