libc++_shared.so not 16 KB aligned on Axmol 2.5.0 builds

[arungowda09]

Axmol version: 2.5.0
NDK version(s) tested:
r25 (25.2.9519653) → build succeeds but libc++_shared.so is not 16 KB aligned

Problem
When analyzing the APK with Android Studio APK Analyzer, I get this warning:

APK make-money-debug.apk is not compatible with 16 KB devices.
Some libraries have LOAD segments not aligned at 16 KB boundaries:
dump_syms/linux/dump_syms.bin
lib/arm64-v8a/libc++_shared.so

The main issue is libc++_shared.so not aligned to 16 KB page size.

Which NDK version do you officially recommend for Axmol 2.5.0 with 16 KB page-size compliance?
(Docs currently mention “23.3 NDK” but there is no such version.)

[halx99]

You need use ndk-r27+ if you not use ./setup.ps1 -p android to install ndk-r23d from ci.android.com
BTW: axmol-2.x recommend ndk is ndk-r23d from ci.android.com which will be auto setup by axmol cmdline: ./setup.ps1 -p android

[arungowda09]

I see, thanks for clarifying!
I’m currently building with NDK r28 and it works fine no crashes.
So just to confirm, is it safe to continue using r28 with Axmol 2.5.0, especially for the upcoming 16 KB page-size requirement?

[halx99]

I see, thanks for clarifying! I’m currently building with NDK r28 and it works fine no crashes. So just to confirm, is it safe to continue using r28 with Axmol 2.5.0, especially for the upcoming 16 KB page-size requirement?

The NDK version depends on the minimum Android version you need to support. Axmol 2.x defaults to NDK r23d for maximum device compatibility (down to Android 4.2). If you don’t need to support such old versions, you can use a newer NDK. For example, Axmol v3 will default to NDK r27d and officially set the minimum supported Android version to 5.1 in future releases.

In short: The engine defaults to a lower Android version for broader compatibility, but you can choose a higher minimum Android version — which in turn determines the NDK version.