New Features of NDK r6

With the support for native activities In r5, the attention to ndk is tight, so I hope to have more support for c and c ++. The following is the description of r6 in changes.html.

Android-ndk-r6

Important changes:
-Official support for the x86 ABI.
This release of the Android NDK now provides support for the 'x86 'ABI.
This allows you to generate machine code that runs on future x86-based
Android devices.

Note that by default, code is still generated for ARM-based devices.
You can however add 'x86 'to your APP_PLATFORM definition in your
Application. mk. For example, the following line instructs ndk-build
To build your code for three distinct ABIs:

APP_ABI: = armeabi armeabi-v7a x86

Unless you rely on ARM-based assembly sources, you shouldn't need to touch
Your Android. mk files to build x86 machine code.

For all details regarding x86 support, please read the new documentation
File named docs/CPU-X86.html.

Don't hesitate to file NDK bugs related to x86 at http:// B .android.com

-You can build a standalone x86 toolchain using the -- toolchain = x86-4.4.3
Option when calling make-standalone-toolchain.sh. See
Docs/STANDALONE-TOOLCHAIN.html for more details.

-The new 'ndk-stack' tool can be used to translate stack traces
(As reported by adb logcat in case of crash in native code)
Something more readable, I. e. containing function/source file/
Line number information corresponding to each stack frame.

For more information and usage example, see the new documentation
File docs/NDK-STACK.html

Other fixes & CHANGES:
-The arm-eabi-4.4.0, which had been deprecated since NDK r5, has been
Finally removed from the NDK distribution.

The main idea is as follows:

Important changes:

-X86 ABI is officially supported.

The new Android NDK version now supports x86 ABI.
This allows your generated machine code to run on an Android device based on the x86 architecture in the future.

Note that the Code still generates ARM-based devices by default. However, you can add 'x86 'to the APP_PLATFORM definition in Application. mk '.
For example, the following line instructs ndk-build to build your code to three different ABI:
APP_ABI: = armeabi armeabi-v7a x86

Unless you rely on ARM-based assembly sources, you do not need to worry about Android. mk to build x86 machine code.

For more information about the x86's support, read the cpu-x86.html file in the docsfile.

For x86 bugs, please do not hesitate to archive in http:// B .android.com
-You can build a separate x86 toolchain that uses the -- toolchain = make-standalone-toolchain.sh option when calling the x86-4.4.3.
For details, see docs/STANDALONE-TOOLCHAIN.html.

-The new "ndk stack" tool can translate stack traces (adb logcat reports when native code crash) for more readable information.
That is, the frame of each stack corresponding to the function/source file/number of rows.

For more information and usage examples, read the new documentation docs/NDK-STACK.html.

Other FIXES & CHANGES:
-Arm-eabi-4.4.0, from NDK r5 is obsolete (deprecated) and has been permanently removed from the NDK distribution.