-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android: arm64 support #154
Comments
Ok, so what do we have to do practically? Is this an NDK thing that we have to add to in gradle? By we, I mean @mortend via Uno 😄 ~ https://stackoverflow.com/a/54474417/2139770 |
I see there's an APK analyzer: https://developer.android.com/studio/build/apk-analyzer |
Here's the android docs reference for telling gradle to build 64bit version of NDK libs: https://developer.android.com/distribute/best-practices/develop/64-bit#building_with_android_studio_or_gradle |
I guess we need to build aarch64 versions of uno-base and other dependencies? |
@kusma is correct. In addition we may have to generate both armv7 and arm64 code and include both in the app in order to not break support for older devices. This will almost double the time it takes to build though, at least on release builds... |
Darn it, will this also inflate app size too? I found this attribute(https://developer.android.com/reference/android/R.attr.html#extractNativeLibs) we can add to the |
I briefly read something a long time ago where (if I remember correctly) it sounded like the Play Store can split the APK and install only one part based on what device the user have. If this is how it works it won't inflate app sizes for end-users downloading apps, but it will inflate the size of the master APK uploaded to Play Store. |
Yeah... Google Play now has shown warning messages about this, as mention it in a forum post here |
See https://github.com/android-ndk/ndk/wiki/Changelog-r19
The text was updated successfully, but these errors were encountered: