1. 26cae16  Merge "Don't pass arch to gdb" by Josh Gao - 12 hours ago master
  2. a9d43ad  Don't pass arch to gdb by Josh Gao - 12 hours ago
  3. 23eef2b  Merge "Address missed comments from build_support CL." by Dan Albert - 15 hours ago
  4. 234ad0f  Merge changes I1d987ea1,I5d0f0c0b,I0af79915,If0c44e15,I83b1c96e, ... by Dan Albert - 15 hours ago
  5. 6aa01b6  Address missed comments from build_support CL. by Dan Albert - 15 hours ago

Android Native Development Kit (NDK)

The NDK allows Android application developers to include native code in their Android application packages, compiled as JNI shared libraries.

See the Getting Started Guide for an introduction.

See the changelist for a list of changes since the previous release.

Finally, discussions related to the Android NDK happen on the android-ndk Google Group.

Building the NDK

Note: This document is for developers of the NDK, not developers that use the NDK.

Both Linux and Windows host binaries are built on Linux machines. Windows host binaries are built via MinGW cross compiler. Systems without a working MinGW compiler can use build/tools/ to generate their own and be added to the PATH for build scripts to discover.

Building binaries for Mac OS X requires at least 10.8.

Target headers and binaries are built on Linux.


The NDK consists of three parts: host binaries, target prebuilts, and others (build system, docs, samples, tests).

Host Binaries

Target Headers and Binaries



Host/Target prebuilts

For Linux or Darwin:

$ python --no-package

For Windows, from Linux:

$ python --system windows


The simplest way to package an NDK on Linux is to just omit the --no-package flag when running This will take a little longer though, so it may not be desired for day to day development.

To package the NDK for Windows or Darwin (or if more control over the packaging process is needed), invoke build/tools/ directly. This process will be improved in a future commit.

Best Practices for Incremental Builds