5 ms·
Until apps start adding native code via the NDK, then you need one binary per arch
by arjvik 4y ago
Until apps start adding native code via the NDK, then you need one binary per arch
- pjmlp 4y agoUnless one is a game developer, otherwise using the NDK is an exercise in masochism. In any case, Intel devices used to have ARM emulators, and Android on ChromeOS still does it. https://developer.android.com/topic/arc/device-support#arm-translation https://developer.android.com/topic/arc/device-support#arm-t...
- saagarjha 4y agoThe NDK is important to applications looking to reuse native codebases.
- pjmlp 4y agoWhile having the joy to manually write JNI wrappers to 90% of Android APIs, and fitting their build into CMake/Gradle scripts, or trying to fit building artifacts into AARs. It might be relevant, however Google's own documentation and tooling during the last decade is quite clear that one should stay out unless doing games.
- saagarjha 4y agoI’m not saying it doesn’t suck, but when has any developer listened to what the platform asks them to do?