Android NDK

The NDK is a toolset that allows you to implement parts  of your app using native-code languages such as C and C++. For certain types of apps,  this can be helpful so you can reuse existing code libraries written in these  languages, but most apps do not need the Android NDK.

Before downloading the NDK, you should understand that the NDK   will not benefit most apps. As a developer, you need to balance its benefits  against its drawbacks. Notably, using native code on Android  generally does not result in a noticable performance improvement,  but it always increases your app complexity. In general, you should only use the NDK  if it is essential to your app—never because you simply prefer to program in C/C++.

Typical good candidates for the NDK are self-contained, CPU-intensive operations that don’t  allocate much memory, such as signal processing, physics simulation, and so on. When examining  whether or not you should develop in native code, think about your requirements and see if the  Android framework APIs provide the functionality that you need.


Platform Package Size MD5 Checksum
Windows 32-bit 434701805 bytes fb41ed2bff5610b14a7b6f085ab86213
Windows 64-bit 461298980 bytes 11eb99b3b56fc86d9d231ebff5c41db3
Mac OS X 32-bit android-ndk-r8e-darwin-x86.tar.bz2 496238878 bytes e17e707464c45c0d5615e4d0ae6a5cf7
Mac OS X 64-bit android-ndk-r8e-darwin-x86_64.tar.bz2 508419298 bytes efac96fab20e6ddb1311d6ba5648ce72
Linux 32-bit (x86) android-ndk-r8e-linux-x86.tar.bz2 461526099 bytes 26d774b0884bcd98de08eb4de41ab532
Linux 64-bit (x86) android-ndk-r8e-linux-x86_64.tar.bz2 466853553 bytes fa812352956067e7a9eefc0274675e9a


The sections below provide information and notes about successive releases of the NDK, as denoted by revision number.

Android NDK, Revision 8e (March 2013)

Important changes:
  • Added 64-bit host toolchain set (package name suffix *-x86_64.*). For more            information, see CHANGES.HTML and NDK-BUILD.html.
  • Added Clang 3.2 compiler. GCC 4.6 is still the default. For information on using the            Clang compiler, see CHANGES.HTML.
  • Added static code analyzer for Linux/MacOSX hosts. For information on using the            analyzer, see CHANGES.HTML.
  • Added MCLinker for Linux/MacOSX hosts as an experimental feature. The            linker is the default where available, so you must explicitly enable it. For more            information, see CHANGES.HTML.
  • Updated ndk-build to use topological sort for module dependencies, which means the            build automatically sorts out the order of libraries specified in            LOCAL_STATIC_LIBRARIES, LOCAL_WHOLE_STATIC_LIBRARIES and            LOCAL_SHARED_LIBRARIES. For more information, see CHANGES.HTML.            (Issue 39378)
Important bug fixes:
  • Fixed build script to build all toolchains in -O2. Toolchains in previous            releases were incorrectly built without optimization.
  • Fixed build script which unconditionally builds Clang/llvm for MacOSX in 64-bit.
  • Fixed GCC 4.6/4.7 internal compiler error:            gen_thumb_movhi_clobber at config/arm/            (Issue 52732)
  • Fixed build problem where GCC/ARM 4.6/4.7 fails to link code using 64-bit atomic            built-in functions.            (Issue 41297)
  • Fixed GCC 4.7 linker DIV usage mismatch errors.          (Sourceware Issue)
  • Fixed GCC 4.7 internal compiler error build_data_member_initialization, at            cp/semantics.c:5790.
  • Fixed GCC 4.7 internal compiler error redirect_eh_edge_1, at tree-eh.c:2214.            (Issue 52909)
  • Fixed a GCC 4.7 segfault.            (GCC Issue)
  • Fixed <chrono> clock resolution and enabled steady_clock.            (Issue 39680)
  • Fixed toolchain to enable _GLIBCXX_HAS_GTHREADS for GCC 4.7 libstdc++.            (Issue 41770,             Issue 41859)
  • Fixed problem with the X86 MXX/SSE code failing to link due to missing            posix_memalign.            (Change 51872)
  • Fixed GCC4.7/X86 segmentation fault in i386.c, function            distance_non_agu_define_in_bb().            (Change 50383)
  • Fixed GCC4.7/X86 to restore earlier cmov behavior.            (GCC Issue)
  • Fixed handling NULL return value of setlocale() in libstdc++/GCC4.7.            (Issue 46718)
  • Fixed runtime undefined reference to __exidx_start and            __exidx_start_end.            (Change 52134)
  • Fixed Clang 3.1 internal compiler error when using Eigen library.            (Issue 41246)
  • Fixed Clang 3.1 internal compiler error including <chrono> in C++11 mode.            (Issue 39600)
  • Fixed Clang 3.1 internal compiler error when generating object code for a method            call to a uniform initialized rvalue.            (Issue 41387)
  • Fixed Clang 3.1/X86 stack realignment.            (Change 52154)
  • Fixed problem with GNU Debugger (GDB) SIGILL when debugging on Android 4.1.2.            (Issue 40941)
  • Fixed problem where GDB cannot set source:line breakpoints when symbols contain            long, indirect file paths.            (Issue 42448)
  • Fixed GDB read_program_header for MIPS PIE executables.            (Change 49592)
  • Fixed STLport segmentation fault in uncaught_exception().            (Change 50236)
  • Fixed STLport bus error in exception handling due to unaligned access of            DW_EH_PE_udata2, DW_EH_PE_udata4, and DW_EH_PE_udata8.
  • Fixed Gabi++ infinite recursion problem with nothrow new[] operator.            (Issue 52833)
  • Fixed Gabi++ wrong offset to exception handler pointer.            (Change 53446)
  • Removed Gabi++ redundant free on exception object            (Change 53447)
Other bug fixes:
  • Fixed NDK headers:
    • Removed redundant definitions of size_t, ssize_t, and                ptrdiff_t.
    • Fixed MIPS and ARM fenv.h header.
    • Fixed stddef.h to not redefine offsetof since it already exists                in the toolchain.
    • Fixed elf.h to contain Elf32_auxv_t and Elf64_auxv_t.                (Issue 38441)
    • Fixed the #ifdef C++ definitions in the                OpenSLES_AndroidConfiguration.h header file.                (Issue 53163)
  • Fixed STLport to abort after out of memory error instead of silently exiting.
  • Fixed system and Gabi++ headers to be able to compile with API level 8 and lower.
  • Fixed cpufeatures to not parse /proc/self/auxv.            (Issue 43055)
  • Fixed to not depend on host libstdc++ and on Windows platforms,            to not depend on the libgcc_sjlj_1.dll library.
  • Fixed Clang 3.1 which emits inconsistent register list in .vsave and fails            assembler.            (Change 49930)
  • Fixed Clang 3.1 to be able to compile libgabi++ and pass the test-stlport            tests for MIPS build targets.            (Change 51961)
  • Fixed Clang 3.1 to only enable exception by default for C++, not for C.
  • Fixed several issues in Clang 3.1 to pass most GNU exception tests.
  • Fixed scripts clang and clang++ in standalone NDK compiler to detect            -cc1 and to not specify -target when found.
  • Fixed ndk-build to observe NDK_APP_OUT set in
  • Fixed X86 and lib.a which were missing the sigsetjmp            and siglongjmp functions already declared in setjmp.h.            (Issue 19851)
  • Patched GCC 4.4.3/4.6/4.7 libstdc++ to work with Clang in C++ 11.            (Clang Issue)
  • Fixed cygwin path in argument passed to HOST_AWK.
  • Fixed ndk-build script warning in windows when running from project’s JNI            directory.            (Issue 40192)
  • Fixed problem where the ndk-build script does not build if makefile has            trailing whitespace in the LOCAL_PATH definition.            (Issue 42841)
Other changes:
  • Enabled threading support in GCC/MIPS toolchain.
  • Updated GCC exception handling helpers __cxa_begin_cleanup and            __cxa_type_match to have default visibility from the previous            hidden visibility in GNU libstdc++. For more information, see            CHANGES.HTML.
  • Updated build scripts so that Gabi++ and STLport static libraries are now built with            hidden visibility except for exception handling helpers.
  • Updated build so that STLport is built for ARM in Thumb mode.
  • Added support for std::set_new_handler in Gabi++.            (Issue 52805)
  • Enabled FUTEX system call in GNU libstdc++.
  • Updated ndk-build so that it  no longer copies prebuilt static library to            a project’s obj/local/<abi>/ directory.            (Issue 40302)
  • Removed __ARM_ARCH_5*__ from ARM toolchains/*/ script.            (Issue 21132)
  • Built additional GNU libstdc++ libraries in thumb for ARM.
  • Enabled MIPS floating-point madd/msub/nmadd/nmsub/recip/rsqrt            instructions with 32-bit FPU.
  • Enabled graphite loop optimizer in GCC 4.6 and 4.7 to allow more optimizations:            -fgraphite, -fgraphite-identity, -floop-block, -floop-flatten,            -floop-interchange, -floop-strip-mine, -floop-parallelize-all,            and -ftree-loop-linear.            (info)
  • Enabled polly for Clang 3.1 on Linux and Max OS X 32-bit hosts which analyzes            and optimizes memory access. (info)
  • Enabled -flto in GCC 4.7, 4.6, Clang 3.2 and Clang 3.1 on linux (Clang LTO            via MIPS compiler targets are not supported because            is not available.
  • Enabled --plugin and --plugin-opt for in GCC 4.6/4.7.
  • Enabled --text-reorder for in GCC 4.7.
  • Configured GNU libstdc++ with _GLIBCXX_USE_C99_MATH which undefines the            isinf script in the bionic header. For more information, see            CHANGES.html.
  • Added APP_LDFLAGS to the build scripts. For more information, see            ANDROID-MK.html.
  • Updated build scripts to allow NDK_LOG=0 to disable the NDK_LOG.
  • Updated build scripts to allow NDK_HOST_32BIT=0 to disable the host developer            environment 32-bit toolchain.
  • Changed the default GCC/X86 flags -march= and -mtune= from            pentiumpro and generic to i686 and atom.
  • Enhanced toolchain build scripts:
    • Fixed a race condition in for the mingw build type                which was preventing a significant amount of parallel build processing.
    • Updated and so they can now run                from the NDK package.                (Issue 52835)
    • Fixed in the MSys utilities collection.
    • Improved 64-bit host toolchain and Canadian Cross build support.
    • Updated script to more recent version.
    • Added option to build libgnustl_static.a and stlport_static.a                without hidden visibility.

Android NDK, Revision 8d (December 2012)

Important changes:
  • Added the GNU Compiler Collection (GCC) 4.7 compiler to the NDK. The GCC 4.6 compiler            is still the default, so you must to explicitly enable the new version as follows:
    • For ndk-build, export the NDK_TOOLCHAIN_VERSION=4.7 variable                or add it to
    • For standalone builds, add the --toolchain= option to      , for example:

    Note: This feature is experimental. Please try it and              report any issues.

  • Added stlport exception support via gabi++.  Note that the new gabi++            depends on dlopen and related code, meaning that:
    • You can no longer build a static executable using the -static                option or include libstlport_static.a using                APP_STL := stlport_static. (You can still use the -static option                with a standalone toolchain.) Compiling a dynamic executable using                include $(BUILD_EXECUTABLE) continues to work because the compiler                automatically adds the -ldl option.
    • If your project links using -nostdlib and {-Wl,–no-undefined}, you                must manually include the -ldl option.

    For more information, see CPLUSPLUS-SUPPORT.html.Note: This feature is experimental and works better with the GCC                4.6/4.7 compilers than with GCC 4.4.3 or Clang 3.1. Please try it and                report any issues.

  • Added a -mstack-protector-guard= option for x86 to choose between a            global default path which is compatible with older Android C library (bionic)            and a new tls path (%gs:20) for -fstack-protector,            -fstack-protector-all and -fstack-protector-strong using the GCC 4.6            and higher compilers.Note: The -mstack-protector-guard setting itself does not              enable any -fstack-protector* options.
  • Added android_setCpu() function to            sources/android/cpufeatures/cpu-features.c for use when auto-detection via            /proc is not possible in Android 4.1 and higher.            (Chromium Issue            164154)
Important bug fixes:
  • Fixed unnecessary rebuild of object files when using the ndk-build script.            (Issue 39810)
  • Fixed a linker failure with the NDK 8c release for Mac OS X 10.6.x that produced the            following error:
    dyld: lazy symbol binding failed: Symbol not found: _memmem Referenced from: ...../arm-linux-androideabi/bin/ld Expected in: /usr/lib/libSystem.B.dylib

    This problem was caused by building on Mac OS X 10.7, which produced binaries that were            not compatible with Mac OS 10.6.x and the NDK.

  • Removed the -x c++ options from the Clang++ standalone build script.          (Issue 39089)
  • Fixed issues using the NDK_TOOLCHAIN_VERSION=clang3.1 option in Cygwin.           (Issue 39585)
  • Fixed the script to allow generation of a            standalone toolchain using the Cygwin or MinGW environments. The resulting toolchain            can be used in Cygwin, MingGW or CMD.exe environments.            (Issue 39915,            Issue 39585)
  • Added missing SL_IID_ANDROIDBUFFERQUEUESOURCE option in android-14 builds for            ARM and X86.            (Issue 40625)
  • Fixed x86 CPU detection for the ANDROID_CPU_X86_FEATURE_MOVBE feature.            (Issue 39317)
  • Fixed an issue preventing the Standard Template Library (STL) from using C++            sources that do not have a .cpp file extension.
  • Fixed GCC 4.6 ARM internal compiler error at reload1.c:1061.            (Issue 20862)
  • Fixed GCC 4.4.3 ARM internal compiler error at emit-rtl.c:1954.            (Issue 22336)
  • Fixed GCC 4.4.3 ARM internal compiler error at postreload.c:396.            (Issue 22345)
  • Fixed problem with GCC 4.6/4.7 skipping lambda functions.            (Issue 35933)
Other bug fixes:
  • NDK header file fixes:
    • Fixed __WINT_TYPE__ and wint_t to be the same type.
    • Corrected typo in android/bitmap.h.                (Issue 15134)
    • Corrected typo in errno.h.
    • Added check for the presence of __STDC_VERSION__ in sys/cdefs.h.                (Issue 14627)
    • Reorganized headers in byteswap.h and dirent.h.
    • Fixed limits.h to include page.h which provides PAGE_SIZE                settings.                (Issue 39983)
    • Fixed return type of glGetAttribLocation() and                glGetUniformLocation() from int to GLint.
    • Fixed __BYTE_ORDER constant for x86 builds.                (Issue 39824)
  • Fixed ndk-build script to not overwrite -Os with -O2 for ARM            builds.
  • Fixed build scripts to allow overwriting of HOST_AWK, HOST_SED, and            HOST_MAKE settings.
  • Fixed issue for on fsck_msdos builds linking objects built by            the Intel C/C++ compiler (ICC).
  • Fixed ARM EHABI support in Clang to conform to specifications.
  • Fixed GNU Debugger (GDB) to shorten the time spent on walking the target’s link map            during solib events.            (Issue 38402)
  • Fixed missing libgcc.a file when linking shared libraries.
Other changes:
  • Backported 64-bit built-in atomic functions for ARM to GCC 4.6.
  • Added documentation for audio output latency, along with other documentation and            fixes.
  • Fixed debug builds with Clang so that non-void functions now raise a SIGILL            signal for paths without a return statement.
  • Updated to accept the suffix -clang3.1            which is equivalent to adding --llvm-version=3.1 to the GCC 4.6 toolchain.
  • Updated GCC and Clang bug report URL to:  
  • Added ARM ELF support to llvm-objdump.
  • Suppressed treating c input as c++ warning for Clang builds.
  • Updated build so that only the 32-bit version of libiberty.a is built and            placed in lib32/.

Android NDK, Revision 8c (November 2012)

Important changes:
  • Added the Clang 3.1 compiler to the NDK. The GNU Compiler Collection (GCC) 4.6 is          still the default, so you must explicitly enable the Clang compiler option as follows:
    • For ndk-build, export NDK_TOOLCHAIN_VERSION=clang3.1 or                add this environment variable setting to
    • For standalone builds, add --llvm-version=3.1 to       and replace CC and CXX in your                makefile with <tool-path>/bin/clang and                <tool-path>/bin/clang++. See STANDALONE-TOOLCHAIN.html for                details.

    Note: This feature is experimental. Please try it and            report any issues.

  • Added Gold linker for the Windows toolchain. Gold linker is also the            default for ARM and X86 on all hosts. You may override it to use the ld.bfd            linker by adding LOCAL_LDFLAGS += -fuse-ld=bfd to, or by passing            -fuse-ld=bfd to the g++/clang++ command line that does the linking.
  • Added checks for spaces in the NDK path to the ndk-build[.cmd] and            ndk-gdb scripts, to prevent build errors that are difficult to diagnose.
  • Made the following changes to API level handling:
    • Modified build logic so that projects that specify android-10 through                android-13 in APP_PLATFORM, or       link against android-9 instead of                android-14.
    • Updated build so that executables using android-16 (Jelly Bean) or higher are                compiled with the -fPIE option for position-independent executables (PIE).                A new APP_PIE option allows you to control this behavior. See APPLICATION-MK.html for details.Note: All API levels above 14 still link against platforms/android-14 and no new platforms/android-N have been added.
    • Modified ndk-build to provide warnings if the adjusted API level is larger              than android:minSdkVersion in the project’s AndroidManifest.xml.
  • Updated the cpu-features helper library to include more ARM-specific features.          See sources/android/cpufeatures/cpu-features.h for details.
  • Modified the long double on the X86 platform to be 8 bytes. This data type is now the          same size as a double, but is still treated as a distinct type.
  • Updated build for APP_ABI=armeabi-v7a:
    • Modified this build type to pass the -march=armv7-a parameter              to the linker. This change ensures that v7-specific libraries and crt*.o are              linked correctly.
    • Added -mfpu=vfpv3-d16 to ndk-build instead of the              -mfpu=vfp option used in previous releases.
Important bug fixes:
  • Fixed an issue where running with root privileges            resulted in the stand alone tool chain being inaccessible to some users.            (Issue 35279)
    • All files and executables in the NDK release package are set to have read and                execute permissions for all.
    • The ownership/group of libstdc++.a is now preserved when copied.
  • Removed redundant \r from Windows prebuilt echo.exe. The redundant          \r caused gdb.setup to fail in the GNU Debugger (GDB) because it          incorrectly became part of the path.          (Issue 36054)
  • Fixed Windows parallel builds that sometimes failed due to timing issues in the          host-mkdir implementation.          (Issue 25875)
  • Fixed GCC 4.4.3 GNU libstdc++ to not merge typeinfo names by          default. For more details, see          toolchain repo gcc/gcc-4.4.3/libstdc++-v3/libsupc++/typeinfo.          (Issue 22165)
  • Fixed problem on null context in GCC 4.6          cp/mangle.c::write_unscoped_name, where GCC may crash when the context is          null and dereferenced in TREE_CODE.
  • Fixed GCC 4.4.3 crashes on ARM NEON-specific type definitions for floats.          (Issue 34613)
  • Fixed the STLport internal _IteWrapper::operator*() implementation          where a stale stack location holding the dereferenced value was returned and caused          runtime crashes.          (Issue 38630)
  • ARM-specific fixes:
    • Fixed ARM GCC 4.4.3/4.6 g++ to not warn that the mangling of              <va_list> was changed in GCC 4.4. The workaround using the              -Wno-psabi switch to avoid this warning is no longer required.
    • Fixed an issue when a project with .arm or .neon suffixes in              LOCAL_SRC_FILES also used APP_STL. With APP_STL, the              ndk-build script searches for C++ files in LOCAL_SRC_FILES before              adding STL header/lib paths to compilation. Modified ndk-build to              filter out .arm and .neon suffixes before the search, otherwise items              in LOCAL_SRC_FILES like myfile.cpp.arm.neon won’t be compiled as C++              code.
    • Fixed binutils-2.21/ld.bfd to be capable of linking object from older              binutils without tag_FP_arch, which was producing assertion fail              error messages in GNU Binutils.              (Issue 35209)
    • Removed Unknown EABI object attribute 44 warning when              binutils-2.19/ld links prebuilt object by newer binutils-2.21
    • Fixed an issue in GNU stdc++ compilation with both -mthumb and              -march=armv7-a, by modifying to populate              headers/libs in sub-directory armv7-a/thumb.              (Issue 35616)
    • Fixed unresolvable R_ARM_THM_CALL relocation error.              (Issue 35342)
    • Fixed internal compiler error at reload1.c:3633, caused by the ARM              back-end expecting the wrong operand type when sign-extend from char.              (GCC Issue 50099)
    • Fixed internal compiler error with negative shift amount.              (GCC Issue)
  • Fixed -fstack-protector for X86, which is also the default for the          ndk-build x86 ABI target.
  • MIPS-specific fixes:
    • Fixed STLport endian-ness by setting _STLP_LITTLE_ENDIAN to 1 when              compiling MIPS libstlport_*.
    • Fixed GCC __builtin_unreachable issue when compiling LLVM.              (GCC Issue 54369)
    • Backported fix for cc1 compile process consuming 100% CPU.              (GCC Issue 50380)
  • GNU Debugger-specific fixes:
    • Disabled Python support in gdb-7.x at build, otherwise the gdb-7.x configure              function may pick up whatever Python version is available on the host and build              gdb with a hard-wired dependency on a specific version of Python.              (Issue 36120)
    • Fixed ndk-gdb when APP_ABI contains all and matchs none              of the known architectures.              (Issue 35392)
    • Fixed Windows pathname support, by keeping the : character if it looks              like it could be part of a Windows path starting with a drive letter.              (GDB Issue 12843)
    • Fixed adding of hardware breakpoint support for ARM in gdbserver.              (GDB Issue)
    • Added fix to only read the current solibs when the linker is consistent.              This change speeds up solib event handling.              (Issue 37677)
    • Added fix to make repeated attempts to find solib breakpoints. GDB now              retries enable_break() during every call to svr4_current_sos() until              it succeeds.              (Change 43563)
    • Fixed an issue where gdb would not stop on breakpoints placed in              dlopen-ed libraries.              (Issue 34856)
    • Fixed SIGILL in dynamic linker when calling dlopen(), on system              where /system/bin/linker is stripped of symbols and              rtld_db_dlactivity() is implemented as Thumb, due to not preserving              LSB of sym_addr.              (Issue 37147)
Other bug fixes:
  • Fixed NDK headers:
    • Fixed arch-mips/include/asm/* code that was incorrectly removed from              original kernel. (Change              43335)
    • Replaced struct member data __unused with __linux_unused in              linux/sysctl.h and linux/icmp.h to avoid conflict with              #define __unused in sys/cdefs.h.
    • Fixed fenv.h for enclosed C functions with __BEGIN_DECLS and              __END_DECLS.
    • Removed unimplemented functions in malloc.h.
    • Fixed stdint.h defintion of uint64_t for ANSI compilers.              (Issue 1952)
    • Fixed preprocessor macros in <arch>/include/machine/*.
    • Replaced link.h for MIPS with new version supporting all platforms.
    • Removed linux-unistd.h
    • Move GLibc-specific macros LONG_LONG_MIN, LONG_LONG_MAX and              ULONG_LONG_MAX from <pthread.h> to <limits.h>.
  • Fixed a buffer overflow in ndk-stack-parser.
  • Fixed _STLP_USE_EXCEPTIONS, when not defined, to omit all declarations          and uses of __Named_exception. Compiling and use of __Named_exception          settings only occurs when STLport is allowed to use exceptions.
  • Fixed building of Linux-only NDK packages without also building Windows code. Use the          following settings to perform this type of build:
    ./build/tools/ --force --systems=linux-x86
  • Fixed so it does not export atexit() and __do_handler.          These symbols are exported for ARM builds by the system version of the C library to          support legacy native libraries. NDK-generated should never reference them directly.          Instead, each shared library or executable should embed its own version of these symbols,          provided by crtbegin_*.o.If your project is linked with the -nostdlib -Wl,--no-undefined options, you          must provide your own __dso_handle because crtbegin_so.o is not linked in          this case. The content of __dso_handle does not matter, as shown in the following          example code:
    extern "C" {   extern void *__dso_handle __attribute__((__visibility__ ("hidden")));   void *__dso_handle; }
  • Fixed symbol decoder for ARM used in objdump for plt entries to          generate a more readable form function@plt.
  • Removed the following symbols, introduced in GCC 4.6 libgcc.a, from          the X86 platform library: __aeabi_idiv0, __aeabi_ldiv0,          __aeabi_unwind_cpp_pr1, and __aeabi_unwind_cpp_pr2.
  • Removed unused .ctors, .dtors, and .eh_frame in MIPS          crt*_so.S.
  • Updated ndk-gdb so that it only takes the last line of output for          ndk-build DUMP_XXXX. This change ensures that if or print something with $(info ...) syntax, it does not get          injected into the result of DUMP_XXXX.          (More info)
Other changes:
  • Removed arch-x86 and arch-mips headers from          platforms/android-[3,4,5,8]. Those headers were incomplete, since both X86 and          MIPS ABIs are only supported at API 9 or higher.
  • Simplified c++ include path in standalone packages, as shown below.          (Issue 35279)
    <path>/arm-linux-androideabi/include/c++/4.6.x-google   to: <path>/include/c++/4.6/
  • Fixed ndk-build to recognize more C++ file extensions by default:          .cc .cp .cxx .cpp .CPP .c++ .C. You may still use LOCAL_CPP_EXTENSION to          overwrite these extension settings.
  • Fixed an issue in samples/san-angeles that caused a black screen or freeze          frame on re-launch.
  • Replaced deprecated APIs in NDK samples.          (Issue 20017)
    • hello-gl2 from android-5 to android-7
    • native-activity from android-9 to android-10
    • native-audio from android-9 to android-10
    • native-plasma from android-9 to android-10
  • Added new branding for Android executables with a simpler scheme in section (defined in crtbegin_static/dynamic.o) so that          debugging tools can act accordingly. The structure member and values are defined as          follows:
    static const struct {   int32_t namesz;  /* = 8,  sizeof ("Android") */   int32_t descsz;  /* = 1 * sizeof(int32_t) */   int32_t type;    /* = 1, ABI_NOTETYPE */   char name[sizeof "Android"];  /* = "Android" */   int32_t android_api; /* = 3, 4, 5, 8, 9, 14 */ }

    The previous branding options in section .note.ABI-tag are deprecated.

  • Added a new script which calls and          standalone/ with various conditions. The script runs          without the --abi option, and is enhanced to compile most of the tests for all          supported ABIs and run on all attached devices

Android NDK, Revision 8b (July 2012)

The main features of this release are a new GNU Compiler Collection (GCC) 4.6 toolchain and GNU Debugger (GDB) 7.3.x which adds debugging support for the Android 4.1 (API Level 16) system image.

Important bug fixes:
  • Fixed LOCAL_SHORT_COMMANDS issues on Mac OS, Windows Cygwin environments for static libraries. List file generation is faster, and it is not regenerated to avoid repeated project rebuilds.
  • Fixed several issues in ndk-gdb:
    • Updated tool to pass flags -e, -d and -s to adb more consistently.
    • Updated tool to accept device serial names containing spaces.
    • Updated tool to retrieve /system/bin/link information, so gdb on the host can set a breakpoint in __dl_rtld_db_dlactivity and be aware of linker activity (e.g., rescan solib symbols when dlopen() is called).
  • Fixed ndk-build clean on Windows, which was failing to remove./libs/*/lib*.so.
  • Fixed ndk-build.cmd to return a non-zero ERRORLEVEL when makefails.
  • Fixed to stop incorrectly exporting the __exidx_start and__exidx_end symbols.
  • Fixed SEGV when unwinding the stack past __libc_init for ARM and MIPS.
Important changes:
  • Added GCC 4.6 toolchain (binutils 2.21 with gold and GDB 7.3.x) to co-exist with the original GCC 4.4.3 toolchain (binutils 2.19 and GDB 6.6).
    • GCC 4.6 is now the default toolchain. You may set NDK_TOOLCHAIN_VERSION=4.4.3 in to select the original one.
    • Support for the gold linker is only available for ARM and x86 architectures on Linux and Mac OS hosts. This support is disabled by default. Add LOCAL_LDLIBS += -fuse-ld=gold in to enable it.
    • Programs compiled with -fPIE require the new GDB for debugging, including binaries in Android 4.1 (API Level 16) system images.
    • The binutils 2.21 ld tool contains back-ported fixes from version 2.22:
      • Fixed ld --gc-sections, which incorrectly retains zombie references to external libraries. (more info).
      • Fixed ARM strip command to preserve the original p_align andp_flags in GNU_RELRO section if they are valid. Without this fix, programs built with -fPIE could not be debugged. (more info)
    • Disabled sincos() optimization for compatibility with older                platforms.
  • Updated build options to enable the Never eXecute (NX) bit and relro/bind_now protections by default:
    • Added --noexecstack to assembler and -z noexecstack to linker that provides NX protection against buffer overflow attacks by enabling NX bit on stack and heap.
    • Added -z relro and  -z now to linker for hardening of internal data sections after linking to guard against security vulnerabilities caused by memory corruption. (more info: 1,2)
    • These features can be disabled using the following options:
      1. Disable NX protection by setting the --execstack option for the assembler and -z execstack for the linker.
      2. Disable hardening of internal data by setting the -z norelro and-z lazy options for the linker.
      3. Disable these protections in the NDK jni/ by setting the following options:
        LOCAL_DISABLE_NO_EXECUTE=true  # disable "--noexecstack" and "-z noexecstack" DISABLE_RELRO=true             # disable "-z relro" and "-z now"

      See docs/ANDROID-MK.html for more details.

  • Added branding for Android executables with the .note.ABI-tag section (incrtbegin_static/dynamic.o) so that debugging tools can act accordingly. The structure member and values are defined as follows:
    static const struct {   int32_t namesz;  /* = 4,  sizeof ("GNU") */   int32_t descsz;  /* = 6 * sizeof(int32_t) */   int32_t type;    /* = 1 */   char  name[sizeof "GNU"];  /* = "GNU" */   int32_t os;      /* = 0 */   int32_t major;   /* = 2 */   int32_t minor;   /* = 6 */   int32_t teeny;   /* = 15 */   int32_t os_variant;  /* = 1 */   int32_t android_api; /* = 3, 4, 5, 8, 9, 14 */ }
Other bug fixes:
  • Fixed mips-linux-gnu relocation truncated to fit R_MIPS_TLS_LDM issue.            (more info)
  • Fixed ld tool segfaults when using --gc-sections.            (more info)
  • Fixed MIPS GOT_PAGE counting issue.            (more info)
  • Fixed follow warning symbol link for mips_elf_count_got_symbols.
  • Fixed follow warning symbol link for mips_elf_allocate_lazy_stub.
  • Moved MIPS .dynamic to the data segment, so that it is writable.
  • Replaced hard-coded values for symbols with correct segment sizes for MIPS.
  • Removed the -mno-shared option from the defaults in the MIPS toolchain. The default for Android toolchain is -fPIC (or -fpic if supported). If you do not explicitly specify -mshared, -fpic, -fPIC, -fpie, or -fPIE, the MIPS compiler adds -mno-shared that turns off PIC. Fixed compiler not to add-mno-shared in this case.
  • Fixed wrong package names in samples hello-jni and two-libs so that the tests project underneath it can compile.
Other Changes:
  • Changed locations of binaries:
    • Moved gdbserver fromtoolchain/<arch-os-ver>/prebuilt/gdbserver toprebuilt/android-<arch>/gdbserver/gdbserver.
    • Renamed x86 toolchain prefix from i686-android-linux- toi686-linux-android-.
    • Moved sources/cxx-stl/gnu-libstdc++/include and lib tosources/cxx-stl/gnu-libstdc++/4.6 when compiled with GCC 4.6, orsources/cxx-stl/gnu-libstdc++/4.4.3 when compiled with GCC 4.4.3.
    • Moved libbfd.a and libintl.a from lib/ to lib32/.
  • Added and improved various scripts in the rebuild and test NDK toolchain:
    • Added to generate a new Linux-hosted toolchain that generates Win32 and Win64 executables.
    • Improved speed of by using the clone command and only using checkout for the directories that are needed to build the NDK toolchain binaries.
    • Added and scripts.
    • Added tests/ to check the content of a given NDK installation directory, or an existing NDK package.
    • Rewrote the tests/standalone/ standalone tests .
  • Removed if_dl.h header from all platforms and architectures. The AF_LINK and sockaddr_dl elements it describes are specific to BSD (i.e., they don’t exist in Linux).

Android NDK, Revision 8 (May 2012)

This release of the NDK includes support for MIPS ABI and a few additional fixes.

New features:
  • Added support for the MIPS ABI, which allows you to generate machine code that runs on            compatible MIPS-based Android devices. Major features for MIPS include MIPS-specific            toolchains, system headers, libraries and debugging support. For more details regarding            MIPS support, see docs/CPU-MIPS.html in the NDK package.By default, code is generated for ARM-based devices. You can add mips to              your APP_ABI definition in your file to build              for MIPS platforms. For example, the following line instructs ndk-build              to build your code for three distinct ABIs:
    APP_ABI := armeabi armeabi-v7a mips

    Unless you rely on architecture-specific assembly sources, such as ARM assembly              code, you should not need to touch your files to build MIPS              machine code.

  • You can build a standalone MIPS toolchain using the --arch=mips          option when calling See          docs/STANDALONE-TOOLCHAIN.html for more details.

Note: To ensure that your applications are available to users only if their devices are capable of running them, Google Play filters applications based on the instruction set information included in your application ? no action is needed on your part to enable the filtering. Additionally, the Android system itself also checks your application at install time and allows the installation to continue only if the application provides a library that is compiled for the device’s CPU architecture.

Important bug fixes:
  • Fixed a typo in GAbi++ implementation where the result of dynamic_cast<D>(b) of base class object b to derived class D is          incorrectly adjusted in the opposite direction from the base class.          (Issue 28721)
  • Fixed an issue in which fails to copy          libsupc++.*.
Other bug fixes:
  • Fixed ndk-build.cmd to ensure that ndk-build.cmd works correctly even          if the user has redefined the SHELL environment variable, which may be changed          when installing a variety of development tools in Windows environments.

Android NDK, Revision 7c (April 2012)

This release of the NDK includes an important fix for Tegra2-based devices, and a few additional fixes and improvements:

Important bug fixes:
  • Fixed GNU STL armeabi-v7a binaries to not crash on non-NEON  devices. The files provided with NDK r7b were not configured properly,  resulting in crashes on Tegra2-based devices and others when trying to use  certain floating-point functions (e.g., cosf, sinf, expf).
Important changes:
  • Added support for custom output directories through the NDK_OUT  environment variable. When defined, this variable is used to store all  intermediate generated files, instead of $PROJECT_PATH/obj. The variable is  also recognized by ndk-gdb.
  • Added support for building modules with hundreds or even thousands of source  files by defining LOCAL_SHORT_COMMANDS to true in your change forces the NDK build system to put most linker or archiver options  into list files, as a work-around for command-line length limitations.  See docs/ANDROID-MK.html for details.
Other bug fixes:
  • Fixed android_getCpuCount() implementation in the cpufeatureshelper library. On certain devices, where cores are enabled dynamically by the system, the previous implementation would report the total number of active cores the first time the function was called, rather than the total number of physically available cores.

Android NDK, Revision 7b (February 2012)

This release of the NDK includes fixes for native Windows builds, Cygwin and many other      improvements:

Important bug fixes:
  • Updated sys/atomics.h to avoid correctness issues            on some multi-core ARM-based devices. Rebuild your unmodified sources with this            version of the NDK and this problem should be completely eliminated.            For more details, read docs/ANDROID-ATOMICS.html.
  • Reverted to binutils 2.19 to fix debugging issues that            appeared in NDK r7 (which switched to binutils 2.20.1).
  • Fixed ndk-build on 32-bit Linux. A packaging error put a 64-bit version            of the awk executable under prebuilt/linux-x86/bin in NDK r7.
  • Fixed native Windows build (ndk-build.cmd). Other build modes were not            affected. The fixes include:
    • Removed an infinite loop / stack overflow bug that happened when trying                to call ndk-build.cmd from a directory that was not the top of                your project path (e.g., in any sub-directory of it).
    • Fixed a problem where the auto-generated dependency files were ignored. This                meant that updating a header didn’t trigger recompilation of sources that included                it.
    • Fixed a problem where special characters in files or paths, other than spaces and                quotes, were not correctly handled.
  • Fixed the standalone toolchain to generate proper binaries when using            -lstdc++ (i.e., linking against the GNU libstdc++ C++ runtime). You            should use -lgnustl_shared if you want to link against the shared library            version or -lstdc++ for the static version.See docs/STANDALONE-TOOLCHAIN.html for more details about this fix.
  • Fixed gnustl_shared on Cygwin. The linker complained that it couldn’t find            libsupc++.a even though the file was at the right location.
  • Fixed Cygwin C++ link when not using any specific C++ runtime through            APP_STL.
Other changes:
  • When your application uses the GNU libstdc++ runtime, the compiler will            no longer forcibly enable exceptions and RTTI. This change results in smaller code.If you need these features, you must do one of the following:
    • Enable exceptions and/or RTTI explicitly in your modules or       (recommended)
    • Define APP_GNUSTL_FORCE_CPP_FEATURES to 'exceptions',                'rtti' or both in your See                docs/APPLICATION-MK.html for more details.
  • ndk-gdb now works properly when your application has private services            running in independent processes. It debugs the main application process, instead of the            first process listed by ps, which is usually a service process.
  • Fixed a rare bug where NDK r7 would fail to honor the LOCAL_ARM_MODE value            and always compile certain source files (but not all) to 32-bit instructions.
  • STLport: Refresh the sources to match the Android platform version. This            update fixes a few minor bugs:
    • Fixed instantiation of an incomplete type
    • Fixed minor “==” versus “=” typo
    • Used memmove instead of memcpy in string::assign
    • Added better handling of IsNANorINF, IsINF, IsNegNAN,                 etc.

    For complete details, see the commit log.

  • STLport: Removed 5 unnecessary static initializers from the library.
  • The GNU libstdc++ libraries for armeabi-v7a were mistakenly compiled for            armeabi instead. This change had no impact on correctness, but using the right            ABI should provide slightly better performance.
  • The cpu-features helper library was updated to report three optional            x86 CPU features (SSSE3, MOVBE and POPCNT). See            docs/CPU-FEATURES.html for more details.
  • docs/NDK-BUILD.html was updated to mention NDK_APPLICATION_MK instead            of NDK_APP_APPLICATION_MK to select a custom file.
  • Cygwin: ndk-build no longer creates an empty “NUL” file in the current            directory when invoked.
  • Cygwin: Added better automatic dependency detection. In the previous version, it            didn’t work properly in the following cases:
    • When the Cygwin drive prefix was not /cygdrive.
    • When using drive-less mounts, for example, when Cygwin would translate                /home to \\server\subdir instead of C:\Some\Dir.
  • Cygwin: ndk-build does not try to use the native Windows tools under            $NDK/prebuilt/windows/bin with certain versions of Cygwin and/or GNU Make.

Android NDK, Revision 7 (November 2011)

This release of the NDK includes new features to support the Android 4.0 platform as well    as many other additions and improvements:

New features
  • Added official NDK APIs for Android 4.0 (API level 14), which adds the following          native features to the platform:
    • Added native multimedia API based on the Khronos Group OpenMAX AL? 1.0.1              standard. The new <OMXAL/OpenMAXAL.h> and              <OMXAL/OpenMAXAL_Android.h> headers allow applications targeting              API level 14 to perform multimedia output directly from native code by using a new              Android-specific buffer queue interface. For more details, see              docs/openmaxal/index.html and
    • Updated the native audio API based on the Khronos Group OpenSL ES 1.0.1?              standard. With API Level 14, you can now decode compressed audio (e.g. MP3, AAC,              Vorbis) to PCM. For more details, see docs/opensles/index.html and    
  • Added CCache support. To speed up large rebuilds, define the          NDK_CCACHE environment variable to ccache (or the path to          your ccache binary). When declared, the NDK build system automatically          uses CCache when compiling any source file. For example:
    export NDK_CCACHE=ccache

    Note: CCache is not included in the NDK release          so you must have it installed prior to using it. For more information about CCache, see

  • Added support for setting APP_ABI to all to indicate that          you want to build your NDK modules for all the ABIs supported by your given NDK          release. This means that either one of the following two lines in your are equivalent with this release:
    APP_ABI := all APP_ABI := armeabi armeabi-v7a x86

    This also works if you define APP_ABI when calling            ndk-build from the command-line, which is a quick way to check that your            project builds for all supported ABIs without changing the project’s   file. For example:

    ndk-build APP_ABI=all
  • Added a LOCAL_CPP_FEATURES variable in that          allows you to declare which C++ features (RTTI or Exceptions) your module uses. This          ensures that the final linking works correctly if you have prebuilt modules that depend          on these features. See docs/ANDROID-MK.html and          docs/CPLUSPLUS-SUPPORT.html for more details.
  • Shortened paths to source and object files that are used in build commands. When          invoking $NDK/ndk-build from your project path, the paths to the source,          object, and binary files that are passed to the build commands are significantly          shorter now, because they are passed relative to the current directory. This is useful          when building projects with a lot of source files, to avoid limits on the maximum          command line length supported by your host operating system. The behavior is unchanged          if you invoke ndk-build from a sub-directory of your project tree, or if          you define NDK_PROJECT_PATH to point to a specific directory.
Experimental features
        You can now build your NDK source files on Windows without Cygwin by calling the        ndk-build.cmd script from the command line from your project path. The        script takes exactly the same arguments as the original ndk-build script.        The Windows NDK package comes with its own prebuilt binaries for GNU Make, Awk and other        tools required by the build. You should not need to install anything else to get a        working build system.Important: ndk-gdb does not work on        Windows, so you still need Cygwin to debug.

This feature is still experimental, so feel free to try it and report issues on the        public bug database or public forum. All samples and unit tests        shipped with the NDK succesfully compile with this feature.

Important bug fixes
  • Imported shared libraries are now installed by default to the target installation          location (libs/<abi>) if APP_MODULES is not defined in          your For example, if a top-level module foo          imports a module bar, then both and are copied to the install location. Previously, only was copied, unless you listed bar in your          APP_MODULES too. If you define APP_MODULES explicitly, the          behavior is unchanged.
  • ndk-gdb now works correctly for activities with multiple categories in          their MAIN intent filters.
  • Static library imports are now properly transitive. For example, if a top-level          module foo imports static library bar that imports static          library zoo, the will now be linked against both          libbar.a and libzoo.a.
Other changes
  • docs/NATIVE-ACTIVITY.HTML: Fixed typo. The minimum API level should be          9, not 8 for native activities.
  • docs/STABLE-APIS.html: Added missing documentation listing EGL as a          supported stable API, starting from API level 9.
  • Updated to download the toolchain          sources from,          which is the new location for the AOSP servers.
  • Added a new C++ support runtime named gabi++. More details about it          are available in the updated docs/CPLUSPLUS-SUPPORT.html.
  • Added a new C++ support runtime named gnustl_shared that corresponds          to the shared library version of GNU libstdc++ v3 (GPLv3 license). See more info at          docs/CPLUSPLUS-SUPPORT.html
  • Added support for RTTI in the STLport C++ runtimes (no support for          exceptions).
  • Added support for multiple file extensions in LOCAL_CPP_EXTENSION. For          example, to compile both foo.cpp and bar.cxx as C++ sources,          declare the following:
    LOCAL_CPP_EXTENSION := .cpp .cxx
  • Removed many unwanted exported symbols from the link-time shared system libraries          provided by the NDK. This ensures that code generated with the standalone toolchain          doesn’t risk to accidentally depend on a non-stable ABI symbol (e.g. any libgcc.a          symbol that changes each time the toolchain used to build the platform is changed)
  • Refreshed the EGL and OpenGLES Khronos headers to support more extensions. Note          that this does not change the NDK ABIs for the corresponding libraries,          because each extension must be probed at runtime by the client application.The extensions that are available depend on your actual device and GPU drivers,            not the platform version the device runs on. The header changes simply add new            constants and types to make it easier to use the extensions when they have been            probed with eglGetProcAddress() or glGetProcAddress(). The            following list describes the newly supported extensions:
    GLES 1.x
    • GL_OES_vertex_array_object
    • GL_OES_EGL_image_external
    • GL_APPLE_texture_2D_limited_npot
    • GL_EXT_blend_minmax
    • GL_EXT_discard_framebuffer
    • GL_EXT_multi_draw_arrays
    • GL_EXT_read_format_bgra
    • GL_EXT_texture_filter_anisotropic
    • GL_EXT_texture_format_BGRA8888
    • GL_EXT_texture_lod_bias
    • GL_IMG_read_format
    • GL_IMG_texture_compression_pvrtc
    • GL_IMG_texture_env_enhanced_fixed_function
    • GL_IMG_user_clip_plane
    • GL_IMG_multisampled_render_to_texture
    • GL_NV_fence
    • GL_QCOM_driver_control
    • GL_QCOM_extended_get
    • GL_QCOM_extended_get2
    • GL_QCOM_perfmon_global_mode
    • GL_QCOM_writeonly_rendering
    • GL_QCOM_tiled_rendering
    GLES 2.0
    • GL_OES_element_index_uint
    • GL_OES_get_program_binary
    • GL_OES_mapbuffer
    • GL_OES_packed_depth_stencil
    • GL_OES_texture_3D
    • GL_OES_texture_float
    • GL_OES_texture_float_linear
    • GL_OES_texture_half_float_linear
    • GL_OES_texture_npot
    • GL_OES_vertex_array_object
    • GL_OES_EGL_image_external
    • GL_AMD_program_binary_Z400
    • GL_EXT_blend_minmax
    • GL_EXT_discard_framebuffer
    • GL_EXT_multi_draw_arrays
    • GL_EXT_read_format_bgra
    • GL_EXT_texture_format_BGRA8888
    • GL_EXT_texture_compression_dxt1
    • GL_IMG_program_binary
    • GL_IMG_read_format
    • GL_IMG_shader_binary
    • GL_IMG_texture_compression_pvrtc
    • GL_IMG_multisampled_render_to_texture
    • GL_NV_coverage_sample
    • GL_NV_depth_nonlinear
    • GL_QCOM_extended_get
    • GL_QCOM_extended_get2
    • GL_QCOM_writeonly_rendering
    • GL_QCOM_tiled_rendering
    • EGL_ANDROID_recordable
    • EGL_NV_system_time

Android NDK, Revision 6b (August 2011)

This release of the NDK does not include any new features compared to r6. The r6b release      addresses the following issues in the r6 release:

Important bug fixes
  • Fixed the build when APP_ABI="armeabi x86" is used for            multi-architecture builds.
  • Fixed the location of prebuilt STLport binaries in the NDK release package.            A bug in the packaging script placed them in the wrong location.
  • Fixed atexit() usage in shared libraries with the x86standalone            toolchain.
  • Fixed --arch=x86. It used to fail            to copy the proper GNU libstdc++ binaries to the right location.
  • Fixed the standalone toolchain linker warnings about missing the definition and            size for the __dso_handle symbol (ARM only).
  • Fixed the inclusion order of $(SYSROOT)/usr/include for x86 builds.            See the bug for            more information.
  • Fixed the definitions of ptrdiff_t and size_t in            x86-specific systems when they are used with the x86 standalone toolchain.

Android NDK, Revision 6 (July 2011)

This release of the NDK includes support for the x86 ABI and other minor changes.      For detailed information describing the changes in this release, read the      CHANGES.HTML document included in the NDK package.

General notes:
  • Adds support for the x86 ABI, which allows you to generate machine code            that runs on compatible x86-based Android devices. Major features for x86            include x86-specific toolchains, system headers, libraries and            debugging support. For all of the details regarding x86 support,            see docs/CPU-X86.html in the NDK package.By default, code is generated for ARM-based devices, but you can add x86 to your              APP_ABI definition in your file to build              for x86 platforms. 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 files to build x86 machine code.

  • You can build a standalone x86 toolchain using the --toolchain=x86-4.4.3            option when calling See            docs/STANDALONE-TOOLCHAIN.html for more details.
  • The new ndk-stack tool lets you translate stack traces in            logcat that are generated by native code. The tool translates            instruction addresses into a readable format that contains things such            as the function, source file, and line number corresponding to each stack frame.            For more information and a usage example, see docs/NDK-STACK.html.
Other changes:
arm-eabi-4.4.0, which had been deprecated since NDK r5, has been        removed from the NDK distribution.

Android NDK, Revision 5c (June 2011)

This release of the NDK does not include any new features compared to r5b. The r5c release    addresses the following problems in the r5b release:

Important bug fixes:
  • ndk-build: Fixed a rare bug that appeared when trying to perform parallel          builds of debuggable projects.
  • Fixed a typo that prevented LOCAL_WHOLE_STATIC_LIBRARIES to work          correctly with the new toolchain and added documentation for this in          docs/ANDROID-MK.html.
  • Fixed a bug where code linked against gnustl_static crashed when run on          platform releases older than API level 8 (Android 2.2).
  • ndk-gdb: Fixed a bug that caused a segmentation fault when debugging Android 3.0          or newer devices.
  • <android/input.h>: Two functions that were introduced in API level          9 (Android 2.3) were incorrect and are fixed. While this breaks the source API, the          binary interface to the system is unchanged. The incorrect functions were missing a          history_index parameter, and the correct definitions are shown below:
    float AMotionEvent_getHistoricalRawX(const AInputEvent* motion_event,                                            size_t pointer_index,                                            size_t history_index);
    float AMotionEvent_getHistoricalRawY(const AInputEvent* motion_event,                                            size_t pointer_index,                                            size_t history_index);
  • Updated the C library ARM binary for API level 9 (Android 2.3) to correctly expose at          link time new functions that were added in that API level (for example,          pthread_rwlock_init).
Minor improvements and fixes:
  • Object files are now always linked in the order they appear in          LOCAL_SRC_FILES. This was not the case previously because the files were          grouped by source extensions instead.
  • When import-module fails, it now prints the list of directories that          were searched. This is useful to check that the NDK_MODULE_PATH definition          used by the build system is correct.
  • When import-module succeeds, it now prints the directory where the          module was found to the log (visible with NDK_LOG=1).
  • Increased the build speed of debuggable applications when there is a very large number          of include directories in the project.
  • ndk-gdb: Better detection of adb shell failures and improved          error messages.
  • <pthread.h>: Fixed the definition of          PTHREAD_RWLOCK_INITIALIZER for API level 9 (Android 2.3) and higher.
  • Fixed an issue where a module could import itself, resulting in an infinite loop in          GNU Make.
  • Fixed a bug that caused the build to fail if LOCAL_ARM_NEON was set to          true (typo in build/core/
  • Fixed a bug that prevented the compilation of .s assembly files          (.S files were okay).

Android NDK, Revision 5b (January 2011)

This release of the NDK does not include any new features compared to r5. The r5b release addresses the      following problems in the r5 release:

  • The r5 binaries required glibc 2.11, but the r5b binaries are generated with a special    toolchain that targets glibc 2.7 or higher instead. The Linux toolchain binaries now run on Ubuntu 8.04 or higher.
  • Fixes a compiler bug in the arm-linux-androideabi-4.4.3 toolchain.    The previous binary generated invalid thumb instruction sequences when    dealing with signed chars.
  • Adds missing documentation for the    “gnustl_static” value for APP_STL, that allows you to link against    a static library version of GNU libstdc++.
  • The following ndk-build issues are fixed:
    • A bug that created inconsistent dependency files when a        compilation error occured on Windows. This prevented a proper build after        the error was fixed in the source code.
    • A Cygwin-specific bug where using very short paths for        the Android NDK installation or the project path led to the        generation of invalid dependency files. This made incremental builds        impossible.
    • A typo that prevented the cpufeatures library from working correctly        with the new NDK toolchain.
    • Builds in Cygwin are faster by avoiding calls to cygpath -m        from GNU Make for every source or object file, which caused problems        with very large source trees. In case this doesn’t work properly, define NDK_USE_CYGPATH=1 in your        environment to use cygpath -m again.
    • The Cygwin installation now notifies the user of invalid installation paths that contain spaces. Previously, an invalid path        would output an error that complained about an incorrect version of GNU Make, even if the right one was installed.
  • Fixed a typo that prevented the NDK_MODULE_PATH environment variable from working properly when  it contained multiple directories separated with a colon.
  • The script contains fixes to check the compiler for 64-bit  generated machine code, instead of relying on the host tag, which  allows the 32-bit toolchain to rebuild properly on Snow Leopard. The toolchain rebuild scripts now also support  using a 32-bit host toolchain.
  • A missing declaration for INET_ADDRSTRLEN was added to <netinet/in.h>.
  • Missing declarations for IN6_IS_ADDR_MC_NODELOCAL and IN6_IS_ADDR_MC_GLOBAL were added to <netinet/in6.h>.
  • ‘asm’ was replaced with ‘__asm__’ in <asm/byteorder.h> to allow compilation with -std=c99.

Android NDK, Revision 5 (December 2010)

This release of the NDK includes many new APIs, most of which are introduced to         support the development of games and similar applications that make extensive use         of native code. Using the APIs, developers have direct native access to events, audio,         graphics and window management, assets, and storage. Developers can also implement the         Android application lifecycle in native code with help from the new         NativeActivity class. For detailed information describing the changes in this         release, read the CHANGES.HTML document included in the downloaded NDK package.

General notes:
  • Adds support for native activities, which allows you to implement the            Android application lifecycle in native code.
  • Adds native support for the following:
    • Input subsystem (such as the keyboard and touch screen)
    • Access to sensor data (accelerometer, compass, gyroscope, etc).
    • Event loop APIs to wait for things such as input and sensor events.
    • Window and surface subsystem
    • Audio APIs based on the OpenSL ES standard that support playback and recording                as well as control over platform audio effects
    • Access to assets packaged in an .apk file.
  • Includes a new toolchain (based on GCC 4.4.3), which generates better code, and can also now            be used as a standalone cross-compiler, for people who want to build their stuff with            ./configure && make. See            docs/STANDALONE-TOOLCHAIN.html for the details. The binaries for GCC 4.4.0 are still provided,            but the 4.2.1 binaries were removed.
  • Adds support for prebuilt static and shared libraries (docs/PREBUILTS.html) and module            exports and imports to make sharing and reuse of third-party modules much easier            (docs/IMPORT-MODULE.html explains why).
  • Provides a default C++ STL implementation (based on STLport) as a helper module. It can be used either            as a static or shared library (details and usage examples are in sources/android/stlport/README). Prebuilt            binaries for STLport (static or shared) and GNU libstdc++ (static only) are also provided if you choose to            compile against those libraries instead of the default C++ STL implementation.            C++ Exceptions and RTTI are not supported in the default STL implementation. For more information, see            docs/CPLUSPLUS-SUPPORT.HTML.
  • Includes improvements to the cpufeatures helper library that improves reporting            of the CPU type (some devices previously reported ARMv7 CPU when the device really was an ARMv6). We            recommend developers that use this library to rebuild their applications then            upload to Google Play to benefit from the improvements.
  • Adds an EGL library that lets you create and manage OpenGL ES textures and              services.
  • Adds new sample applications, native-plasma and native-activity,            to demonstrate how to write a native activity.
  • Includes many bugfixes and other small improvements; see docs/CHANGES.html for a more              detailed list of changes.

Android NDK, Revision 4b (June 2010)

NDK r4b notes:
Includes fixes for several issues in the NDK build and debugging scripts — if          you are using NDK r4, we recommend downloading the NDK r4b build. For detailed          information describing the changes in this release, read the CHANGES.TXT document          included in the downloaded NDK package.

General notes:
  • Provides a simplified build system through the new ndk-build build            command.
  • Adds support for easy native debugging of generated machine code on production            devices through the new ndk-gdb command.
  • Adds a new Android-specific ABI for ARM-based CPU architectures,            armeabi-v7a. The new ABI extends the existing armeabi ABI to            include these CPU instruction set extensions:
    • Thumb-2 instructions
    • VFP hardware FPU instructions (VFPv3-D16)
    • Optional support for ARM Advanced SIMD (NEON) GCC intrinsics and VFPv3-D32.                Supported by devices such as Verizon Droid by Motorola, Google Nexus One, and                others.
  • Adds a new cpufeatures static library (with sources) that lets your            app detect the host device’s CPU features at runtime. Specifically, applications can            check for ARMv7-A support, as well as VFPv3-D32 and NEON support, then provide separate            code paths as needed.
  • Adds a sample application, hello-neon, that illustrates how to use the            cpufeatures library to check CPU features and then provide an optimized            code path using NEON instrinsics, if supported by the CPU.
  • Lets you generate machine code for either or both of the instruction sets supported            by the NDK. For example, you can build for both ARMv5 and ARMv7-A architectures at the            same time and have everything stored to your application’s final            .apk.
  • To ensure that your applications are available to users only if their devices are            capable of running them, Google Play now filters applications based on the            instruction set information included in your application — no action is needed on            your part to enable the filtering. Additionally, the Android system itself also checks            your application at install time and allows the installation to continue only if the            application provides a library that is compiled for the device’s CPU architecture.
  • Adds support for Android 2.2, including a new stable API for accessing the pixel            buffers of Bitmap objects from native code.

Android NDK, Revision 3 (March 2010)

General notes:
  • Adds OpenGL ES 2.0 native library support.
  • Adds a sample application,hello-gl2, that illustrates the use of            OpenGL ES 2.0 vertex and fragment shaders.
  • The toolchain binaries have been refreshed for this release with GCC 4.4.0, which            should generate slightly more compact and efficient machine code than the previous one            (4.2.1). The NDK also still provides the 4.2.1 binaries, which you can optionally use            to build your machine code.

Android NDK, Revision 2 (September 2009)

Originally released as “Android 1.6 NDK, Release 1”.

General notes:
  • Adds OpenGL ES 1.1 native library support.
  • Adds a sample application, san-angeles, that renders 3D graphics            through the native OpenGL ES APIs, while managing activity lifecycle with a GLSurfaceView object.

Android NDK, Revision 1 (June 2009)

Originally released as “Android 1.5 NDK, Release 1”.

General notes:
  • Includes compiler support (GCC) for ARMv5TE instructions, including Thumb-1            instructions.
  • Includes system headers for stable native APIs, documentation, and sample            applications.

System and Software Requirements

The sections below describe the system and software requirements for using the Android NDK, as  well as platform compatibility considerations that affect appplications using libraries produced  with the NDK.

The Android SDK

  • A complete Android SDK installation (including all dependencies) is required.
  • Android 1.5 SDK or later version is required.

Supported operating systems

  • Windows XP (32-bit) or Vista (32- or 64-bit)
  • Mac OS X 10.4.8 or later (x86 only)
  • Linux (32 or 64-bit; Ubuntu 8.04, or other Linux distributions using GLibc 2.7 or later)

Required development tools

  • For all development platforms, GNU Make 3.81 or later is required. Earlier versions of GNU    Make might work but have not been tested.
  • A recent version of awk (either GNU Awk or Nawk) is also required.
  • For Windows, Cygwin 1.7 or higher is required. The NDK    will not work with Cygwin 1.5 installations.

Android platform compatibility

  • The native libraries created by the Android NDK can only be used on devices running      specific minimum Android platform versions. The minimum required platform version depends on      the CPU architecture of the devices you are targeting. The following table details which      Android platform versions are compatible with native code developed for specific CPU      architectures.
    Native Code CPU Architecture Used Compatible Android Platform(s)
    ARM, ARM-NEON Android 1.5 (API Level 3) and higher
    x86 Android 2.3 (API Level 9) and higher
    MIPS Android 2.3 (API Level 9) and higher

    These requirements mean you can use native libraries produced with the NDK in      applications that are deployable to ARM-based devices running Android 1.5 or later. If you are      deploying native libraries to x86 and MIPS-based devices, your application must target Android      2.3 or later.

  • To ensure compatibility, an application using a native library produced with the NDK    must declare a       <uses-sdk> element in its manifest file, with an      android:minSdkVersion attribute value of “3” or higher. For example:
    <manifest>   <uses-sdk android:minSdkVersion="3" />   ... </manifest>
  • If you use this NDK to create a native library that uses the OpenGL ES APIs, the    application containing the library can be deployed only to devices running the minimum platform    versions described in the table below. To ensure compatibility, make sure that your application    declares the proper android:minSdkVersion attribute value, as shown in the    following table.
  • OpenGL ES Version Used Compatible Android Platform(s) Required uses-sdk Attribute
    OpenGL ES 1.1 Android 1.6 (API Level 4) and higher android:minSdkVersion="4"
    OpenGL ES 2.0 Android 2.0 (API Level 5) and higher android:minSdkVersion="5"

    For more information about API Level and its relationship to Android platform versions,      see Android API Levels.

  • Additionally, an application using the OpenGL ES APIs should declare a    <uses-feature> element in its manifest, with an    android:glEsVersion attribute that specifies the minimum OpenGl ES version    required by the application. This ensures that Google Play will show your application only    to users whose devices are capable of supporting your application. For example:
      <uses-feature android:glEsVersion="0x00020000" />   ... </manifest>

    For more information, see the <uses-feature>      documentation.

  • If you use this NDK to create a native library that uses the API to access Android Bitmap pixel buffers or utilizes native activities, the application    containing the library can be deployed only to devices running Android 2.2 (API level 8) or    higher. To ensure compatibility, make sure that your application declares <uses-sdk    android:minSdkVersion="8" /> attribute value in its manifest.

Installing the NDK

Installing the NDK on your development computer is straightforward and involves extracting the  NDK from its download package.

Before you get started make sure that you have downloaded the latest Android SDK and upgraded your applications and environment as  needed. The NDK is compatible with older platform versions but not older versions of the SDK tools.  Also, take a moment to review the System and Software Requirements  for the NDK, if you haven’t already.

To install the NDK, follow these steps:

  1. From the table at the top of this page, select the NDK package that is appropriate for your    development computer and download the package.
  2. Uncompress the NDK download package using tools available on your computer. When    uncompressed, the NDK files are contained in a directory called    android-ndk-<version>. You can rename the NDK directory if necessary and you    can move it to any location on your computer. This documentation refers to the NDK directory as    <ndk>.

You are now ready to start working with the NDK.

Getting Started with the NDK

Once you’ve installed the NDK successfully, take a few minutes to read the documentation included in the NDK. You can find the documentation in the <ndk>/docs/directory. In particular, please read the OVERVIEW.HTML document completely, so that you understand the intent of the NDK and how to use it.

If you used a previous version of the NDK, take a moment to review the list of NDK changes in the CHANGES.HTML document.

Here’s the general outline of how you work with the NDK tools:

  1. Place your native sources under <project>/jni/...
  2. Create <project>/jni/ to describe your native sources to the  NDK build system
  3. Optional: Create <project>/jni/
  4. Build your native code by running the ‘ndk-build’ script from your project’s directory. It  is located in the top-level NDK directory:
    cd <project>

    The build tools copy the stripped, shared libraries needed by your application to the    proper location in the application’s project directory.

  5. Finally, compile your application using the SDK tools in the usual way. The SDK build tools  will package the shared libraries in the application’s deployable .apk file.

For complete information on all of the steps listed above, please see the documentation included with the NDK package.

Using the NDK

The Android framework provides two ways to use native code:

  • Write your application using the Android framework and use JNI to access the APIs provided  by the Android NDK. This technique allows you to take advantage of the convenience of the  Android framework, but still allows you to write native code when necessary. If you use this  approach, your application must target specific, minimum Android platform levels, see Android platform compatibility for more information.
  • Write a native activity, which allows you to implement the lifecycle callbacks in native    code. The Android SDK provides the NativeActivity class, which is a    convenience class that notifies your    native code of any activity lifecycle callbacks (onCreate(), onPause(),    onResume(), etc). You can implement the callbacks in your native code to handle    these events when they occur. Applications that use native activities must be run on Android    2.3 (API Level 9) or later.

    You cannot access features such as Services and Content Providers natively, so if you want    to use them or any other framework API, you can still write JNI code to do so.

Contents of the NDK

The NDK contains the APIs, documentation, and sample  applications that help you write your native code. Specifically:

  • A set of tools and build files used to generate native code libraries from C and C++    sources
  • A way to embed the corresponding native libraries into an application package file    (.apk) that can be deployed on Android devices
  • A set of native system headers and libraries that will be supported in all future versions    of the Android platform, starting from Android 1.5. Applications that use native activities    must be run on Android 2.3 or later.
  • Documentation, samples, and tutorials

The latest release of the NDK supports the following instruction sets:

  • ARMv5TE, including Thumb-1 instructions (see docs/CPU-ARCH-ABIS.html for more information)
  • ARMv7-A, including Thumb-2 and VFPv3-D16 instructions, with optional support for    NEON/VFPv3-D32 instructions (see docs/CPU-ARM-NEON.html for more information)
  • x86 instructions (see docs/CPU-X86.html for more information)
  • MIPS instructions (see docs/CPU-MIPS.html for more information)

ARMv5TE machine code will run on all ARM-based Android devices. ARMv7-A will run only on  devices such as the Verizon Droid or Google Nexus One that have a compatible CPU. The main  difference between the two instruction sets is that ARMv7-A supports hardware FPU, Thumb-2, and  NEON instructions. You can target either or both of the instruction sets — ARMv5TE is the  default, but switching to ARMv7-A is as easy as adding a single line to the application’s file, without needing to change anything else in the file. You can also build for  both architectures at the same time and have everything stored in the final .apk.  Complete information is provided in the CPU-ARCH-ABIS.HTML in the NDK package.

The NDK provides stable headers for libc (the C library), libm (the Math library), OpenGL ES  (3D graphics library), the JNI interface, and other libraries, as listed in the Development tools section.

Development tools

The NDK includes a set of cross-toolchains (compilers, linkers, etc..) that can generate  native ARM binaries on Linux, OS X, and Windows (with Cygwin) platforms.

It provides a set of system headers for stable native APIs that are guaranteed to be supported  in all later releases of the platform:

  • libc (C library) headers
  • libm (math library) headers
  • JNI interface headers
  • libz (Zlib compression) headers
  • liblog (Android logging) header
  • OpenGL ES 1.1 and OpenGL ES 2.0 (3D graphics libraries) headers
  • libjnigraphics (Pixel buffer access) header (for Android 2.2 and above).
  • A Minimal set of headers for C++ support
  • OpenSL ES native audio libraries
  • Android native application APIS

The NDK also provides a build system that lets you work efficiently with your sources, without  having to handle the toolchain/platform/CPU/ABI details. You create very short build files to  describe which sources to compile and which Android application will use them — the build  system compiles the sources and places the shared libraries directly in your application  project.

Important: With the exception of the libraries listed above,  native system libraries in the Android platform are not stable and may change in future  platform versions. Your applications should only make use of the stable native system  libraries provided in this NDK.


The NDK package includes a set of documentation that describes the capabilities of the NDK and  how to use it to create shared libraries for your Android applications. In this release, the  documentation is provided only in the downloadable NDK package. You can find the documentation in  the <ndk>/docs/ directory. Included are these files (partial listing):

  •     INSTALL.HTML — describes how to install the NDK and configure it for your host    system
  • OVERVIEW.HTML — provides an overview of the NDK capabilities and usage
  • ANDROID-MK.HTML — describes the use of the file, which defines the native    sources you want to compile
  • APPLICATION-MK.HTML — describes the use of the file, which describes    the native sources required by your Android application
  • CPLUSPLUS-SUPPORT.HTML — describes the C++ support provided in the Android NDK
  • CPU-ARCH-ABIS.HTML — a description of supported CPU architectures and how to target    them.
  • CPU-FEATURES.HTML — a description of the cpufeatures static library that    lets your application code detect the target device’s CPU family and the optional features at    runtime.
  • CHANGES.HTML — a complete list of changes to the NDK across all releases.
  • DEVELOPMENT.HTML — describes how to modify the NDK and generate release packages for it
  • HOWTO.HTML — information about common tasks associated with NDK development
  • IMPORT-MODULE.HTML — describes how to share and reuse modules
  • LICENSES.HTML  — information about the various open source licenses that govern the Android NDK
  • NATIVE-ACTIVITY.HTML — describes how to implement native activities
  • NDK-BUILD.HTML — describes the usage of the ndk-build script
  • NDK-GDB.HTML — describes how to use the native code debugger
  • PREBUILTS.HTML — information about how shared and static prebuilt libraries work
  • STANDALONE-TOOLCHAIN.HTML — describes how to use Android NDK toolchain as a standalone    compiler (still in beta).
  • SYSTEM-ISSUES.HTML — known issues in the Android system images that you should be    aware of, if you are developing using the NDK.
  • STABLE-APIS.HTML — a complete list of the stable APIs exposed by headers in the    NDK.

Additionally, the package includes detailed information about the “bionic” C library provided  with the Android platform that you should be aware of, if you are developing using the NDK. You  can find the documentation in the <ndk>/docs/system/libc/ directory:

  • OVERVIEW.HTML — provides an overview of the “bionic” C library and the features it    offers.

Sample apps

The NDK includes sample applications that illustrate how to use native code in your Android  applications:

  • hello-jni — a simple application that loads a string from a native    method implemented in a shared library and then displays it in the application UI.
  • two-libs — a simple application that loads a shared library dynamically    and calls a native method provided by the library. In this case, the method is implemented in a    static library imported by the shared library.
  • san-angeles — a simple application that renders 3D graphics through the    native OpenGL ES APIs, while managing activity lifecycle with a GLSurfaceView object.
  • hello-gl2 — a simple application that renders a triangle using OpenGL ES    2.0 vertex and fragment shaders.
  • hello-neon — a simple application that shows how to use the    cpufeatures library to check CPU capabilities at runtime, then use NEON intrinsics    if supported by the CPU. Specifically, the application implements two versions of a tiny    benchmark for a FIR filter loop, a C version and a NEON-optimized version for devices that    support it.
  • bitmap-plasma — a simple application that demonstrates how to access the    pixel buffers of Android Bitmap objects from native code, and uses    this to generate an old-school “plasma” effect.
  • native-activity — a simple application that demonstrates how to use the    native-app-glue static library to create a native activity
  • native-plasma — a version of bitmap-plasma implemented with a native    activity.

For each sample, the NDK includes the corresponding C source code and the necessary  and files. There are located under <ndk>/samples/<name>/  and their source code can be found under <ndk>/samples/<name>/jni/.

You can build the shared libraries for the sample apps by going into  <ndk>/samples/<name>/ then calling the ndk-build command.  The generated shared libraries will be located under  <ndk>/samples/<name>/libs/armeabi/ for (ARMv5TE machine code) and/or  <ndk>/samples/<name>/libs/armeabi-v7a/ for (ARMv7 machine code).

Next, build the sample Android applications that use the shared libraries:

  • If you are developing in Eclipse with ADT, use the New Project Wizard to create a new    Android project for each sample, using the “Import from Existing Source” option and importing    the source from <ndk>/samples/<name>/. Then, set up an AVD,    if necessary, and build/run the application in the emulator.
  • If you are developing with Ant, use the android tool to create the build file    for each of the sample projects at <ndk>/samples/<name>/.    Then set up an AVD, if necessary, build your project in the usual way, and run it in the    emulator.

For more information about developing with the Android SDK tools and what  you need to do to create, build, and run your applications, see  the Overview  section for developing on Android.

Exploring the hello-jni Sample

The hello-jni sample is a simple demonstration on how to use JNI from an Android application.  The HelloJni activity receives a string from a simple C function and displays it in a  TextView.

The main components of the sample include:

  • The familiar basic structure of an Android application (an AndroidManifest.xml    file, a src/ and res directories, and a main activity)
  • A jni/ directory that includes the implemented source file for the native code    as well as the file
  • A tests/ directory that contains unit test code.
  1. Create a new project in Eclipse from the existing sample source or use the    android tool to update the project so it generates a build.xml file that you can    use to build the sample.
    • In Eclipse:
      1. Click File > New Android Project…
      2. Select the Create project from existing source radio button.
      3. Select any API level above Android 1.5.
      4. In the Location field, click Browse… and select            the <ndk-root>/samples/hello-jni directory.
      5. Click Finish.
    • On the command line:
      1. Change to the <ndk-root>/samples/hello-jni directory.
      2. Run the following command to generate a build.xml file:
        android update project -p . -s
  2. Compile the native code using the ndk-build command.
    cd <ndk-root>/samples/hello-jni
  3. Build and install the application as you would a normal Android application. If you are    using Eclipse, run the application to build and install it on a device. If you are using Ant,    run the following commands from the project directory:
    ant debug
    adb install bin/HelloJni-debug.apk

When you run the application on the device, the string Hello JNI should appear on  your device. You can explore the rest of the samples that are located in the  <ndk-root>/samples directory for more examples on how to use the JNI.

Exploring the native-activity Sample Application

The native-activity sample provided with the Android NDK demonstrates how to use the  android_native_app_glue static library. This static library makes creating a native activity  easier by providing you with an implementation that handles your callbacks in another thread, so  you do not have to worry about them blocking your main UI thread. The main parts of the sample  are described below:

  • The familiar basic structure of an Android application (an AndroidManifest.xml    file, a src/ and res directories). The AndroidManifest.xml declares    that the application is native and specifies the .so file of the native activity. See NativeActivity for the source or see the    <ndk_root>/platforms/samples/native-activity/AndroidManifest.xml file.
  • A jni/ directory contains the native activity, main.c, which uses the    android_native_app_glue.h interface to implement the activity. The that    describes the native module to the build system also exists here.

To build this sample application:

  1. Create a new project in Eclipse from the existing sample source or use the    android tool to update the project so it generates a build.xml file that you can    use to build the sample.
    • In Eclipse:
      1. Click File > New Android Project…
      2. Select the Create project from existing source radio button.
      3. Select any API level above Android 2.3.
      4. In the Location field, click Browse… and select            the <ndk-root>/samples/native-activity directory.
      5. Click Finish.
    • On the command line:
      1. Change to the <ndk-root>/samples/native-activity directory.
      2. Run the following command to generate a build.xml file:
        android update project -p . -s
  2. Compile the native code using the ndk-build command.
    cd <ndk-root>/platforms/samples/android-9/samples/native-activity
  3. Build and install the application as you would a normal Android application. If you are    using Eclipse, run the application to build and install it on a device. If you are using Ant,    run the following commands in the project directory, then run the application on the device:
    ant debug
    adb install bin/NativeActivity-debug.apk

Sobre Rosdet Nascimento

Nasci em 1985 em São Tomé e Príncipe, mas vivi toda a minha vida no concelho de Cascais. Tenho formação na área de informática, mas sou administrativo numa grande multinacional, dizem que a maior delas. Além da escrita e do cinema, sou amante de desportos como Running e Krav Maga. Guerreiro é o meu primeiro romance.
Esta entrada foi publicada em Android, Tools. ligação permanente.

Deixe uma Resposta

Preencha os seus detalhes abaixo ou clique num ícone para iniciar sessão:

Logótipo da

Está a comentar usando a sua conta Terminar Sessão /  Alterar )

Google+ photo

Está a comentar usando a sua conta Google+ Terminar Sessão /  Alterar )

Imagem do Twitter

Está a comentar usando a sua conta Twitter Terminar Sessão /  Alterar )

Facebook photo

Está a comentar usando a sua conta Facebook Terminar Sessão /  Alterar )


Connecting to %s