¡@

Home 

2014/10/16 ¤W¤È 08:18:01

android Programming Glossary: local_arm_mode

Android NDK linking

http://stackoverflow.com/questions/10593987/android-ndk-linking

LOCAL_PATH call my dir include CLEAR_VARS LOCAL_C_INCLUDES HEADER FILES LOCAL_MODULE bullet LOCAL_SRC_FILES SRC FILES LOCAL_ARM_MODE arm LOCAL_CFLAGS LOCAL_C_INCLUDES I O3 DANDROID_NDK DDISABLE_IMPORTGL LOCAL_LDLIBS ldl llog include BUILD_SHARED_LIBRARY.. for bullet includes for irrlicht includes for main code LOCAL_SRC_FILES main code src files LOCAL_MODULE gamescript LOCAL_ARM_MODE arm LOCAL_CFLAGS LOCAL_C_INCLUDES I O3 DANDROID_NDK DDISABLE_IMPORTGL LOCAL_LDLIBS lOpenSLES landroid ldl llog LOCAL_SHARED_LIBRARIES..

libjpeg-turbo for android

http://stackoverflow.com/questions/12260149/libjpeg-turbo-for-android

APP_ABI armeabi v7a obj local armeabi v7a libjpeg.a Or compile for ARM to improve performance add to command line LOCAL_ARM_MODE arm If your target has NEON support add to command line LOCAL_ARM_NEON true ARCH_ARM_HAVE_NEON true share improve this..

Producing optimised NDK code for multiple architectures?

http://stackoverflow.com/questions/5089783/producing-optimised-ndk-code-for-multiple-architectures

I've checked all 3 of these speed up my code. Are there any other common ones I could add Another tip I have is to add LOCAL_ARM_MODE arm to Android.mk to enable a speed up on newer arm chips although I'm confused at exactly what this does and what happens.. free . Thumb instructions have their own advantage as well as size they drain the battery less. Anyway this is what LOCAL_ARM_MODE does it means you compile your code as ARM instructions instead of Thumb instructions. Compiling to Thumb is the default.. are supported. ARM can't have NEON without VFPv3. In summary by default your programs are the most compatible. Using LOCAL_ARM_MODE may make things slightly faster at the expense of battery life due to the use of ARM instructions and it is as compatible..