Testing/Enabling armeabi-v7a

[bob-the-hamster]

Currently, python-for-android compiles for armeabi but not for armeabi-v7a

According to this page, armeabi-v7 allows better performance because it can use the FPU
http://stackoverflow.com/questions/7080525/why-use-armeabi-v7a-code-over-armeabi-code

distribute.sh already has support for compiling for armeabi-v7a, but it is commented out. I uncommented and tested it with my game, and it seemed to work great. I have not yet done any profiling to figure out how much (if at all) faster it is.

Would it be best to compile for both? Or to add a command line option to pick between building for one or the other or both?

[knappador]

Docs on what eabi's and a few other options do:
https://gitorious.org/mingw-android-ndk/mingw-android-ndk/source/d086850005e02babf63723eb759242d342e76279:docs/CPU-ARCH-ABIS.html

Note, CPU's such as the Tegra 2 do not support Neon. Android does not have filters for the eabi or the vfpu support level. As such, we use armeabi-v7a with hard floats but only 16 registers. On ARM7-only devices, we get nothing, not even Thumb2.

[inclement]

The new toolchain has an arch toggle and supports both (plux x86 etc).

[ZhangKuixun]

@bob-the-hamster I have same question. How do you build other versions of ABI？