Open opatry opened 9 years ago
or simply use armeabi-v7a-hard
as ANDROID_ABI
which seems to be the value to use in ndk-build
builds
In fact, it might be better to open a dedicated FLOAT_ABI
option used when applicable to keep usage of ${ANDROID_ABI}
variable as output dir (the android packaging expects the libraries to be in libs/armeabi-v7a
, soft or hard float usage.
Hard float and libc++ are not supported by current cmake toolchain. No idea when they will be added as I have almost no time to work on new features.
didn't understood your point… NDK r10d supports hard float (and NDK r10c too I think). Do you talk about something else?
I've seen (l. 1290) that the
ARMEABI_V7A
ABI implies soft float. Is it possible to open another ABI (such asarmeabi-v7a with hardfp
value allowing the use of hard float ABI?