Google Git
Sign in
android / platform / ndk / 05d418635110fe0a5b45670ffe646ff1364a6c22
commit05d418635110fe0a5b45670ffe646ff1364a6c22[log] [tgz]
authorDan Albert <danalbert@google.com>Tue Jul 07 16:50:17 2015 -0700
committerDan Albert <danalbert@google.com>Wed Jul 08 12:22:33 2015 -0700
tree99a6a09a5efc831879b43657cb49b9d23641a652
parent4fd0b3620ebc6bd97a998bc0daad89650bf11798 [diff]
Don't build target prebuilts for Mac or Windows.

We only need one copy of these, and they might as well come from Linux
since that's where we're working. At some point we should probably
transition to using the prebuilt toolchains to build the target
libraries, at which point the target libraries don't need to be
associated with the host build at all.

Change-Id: Ifb5d038e26e2af2ad30e6eef1fc0881a8d66e23f
1 file changed
tree: 99a6a09a5efc831879b43657cb49b9d23641a652
  1. build/
  2. docs/
  3. sources/
  4. tests/
  5. toolchains/
  6. .gitignore
  7. Android.mk
  8. checkbuild.sh
  9. CleanSpec.mk
  10. find-win-host.cmd
  11. GNUmakefile
  12. ndk-build
  13. ndk-build.cmd
  14. ndk-gdb
  15. ndk-gdb-py
  16. ndk-gdb-py.cmd
  17. ndk-gdb.py
  18. ndk-which
  19. README.md
  20. realpath
  21. remove-windows-symlink.sh
README.md

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/build-mingw64-toolchain.sh 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.

Components

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

Host Binaries

  • toolchains/ contains GCC, Clang, and Renderscript toolchains.
    • $TOOLCHAIN/config.mk contains ARCH and ABIS this toolchain can handle.
    • $TOOLCHAIN/setup.mk contains toolchain-specific default CFLAGS/LDFLAGS when this toolchain is used.
  • prebuilt/$HOST_ARCH/ contains various tools to make the build system hermetic.
    • make, awk, sed, perl, python, yasm, and for Windows: cmp.exe and echo.exe
  • prebuilt/common contains the scan-build and scan-view scripts used by static analyzer via NDK_ANALYZE=1.
  • ndk-depends and ndk-stack should probably go in prebuilt/ to avoid collisions between host variants.

Target Headers and Binaries

  • platforms/android-N/arch-$ARCH_NAME/ contains headers and libraries for each API level.
    • The build system sets --sysroot to one of these directories based on user-specified APP_ABI and APP_PLATFORM.
  • sources/cxx-stl/$STL/$ABI/ contains the headers and libraries for the various C++ STLs.
  • prebuilt/android-$ARCH/gdbserver/ contains gdbserver.

Others

  • build/ contains the ndk-build system and scripts to rebuild NDK.
  • docs/
  • samples/
  • sources/ contains modules useful in samples and apps via $(call import-module, $MODULE)
  • tests/

Prerequisites

  • AOSP NDK Repository

    • Check out the branch master-ndk

      repo init -u https://android.googlesource.com/platform/manifest \
    -b master-ndk

# Googlers, use
repo init -u \
    persistent-https://android.git.corp.google.com/platform/manifest \
    -b master-ndk

    • The only difference between the NDK branch and master is that the NDK repository already has the toolchain repository checked out and patched.

  • Additional Linux Dependencies (available from apt):

    • texinfo
    • gcc-mingw32
    • wine
    • bison
    • flex
    • dmake
    • libtool
    • pbzip2

  • Mac OS X also requires Xcode.

Host/Target prebuilts

On Linux:

$ checkbuild.sh --also-64 --systems=linux-x86,windows

On MacOS X:

$ checkbuild.sh --systems=darwin-x86 --try-64
$ checkbuild.sh --systems=darwin-x86

Packaging

Once all prebuilt tarballs are at $PREBUILT_PATH, run the following to package the NDK:

$ build/tools/package-release.sh --prebuilt-dir=/s/prebuilt --separate-64 \
    --release=r9x

Best Practices for Incremental Builds

  • Do not run build/tools/dev-cleanup.sh which erases all prebuilts.
  • Remove the individual prebuilt directory if new build deletes files. This is rare.
  • Package NDK from prebuilt tarballs in $PREBUILT_PATH. It runs build/tools/build-docs.sh which produces no tarball in $PREBUILT_PATH.
  • Unpack and compare against the previous package.