| commit | 6abf81a055fa510794430457c77432ccf12475a4 | [log] [tgz] |
|---|---|---|
| author | Dan Albert <[email protected]> | Thu Dec 03 11:48:48 2015 -0800 |
| committer | Dan Albert <[email protected]> | Thu Dec 03 13:30:31 2015 -0800 |
| tree | 7013037df9a0d57307cb1fd923a271a41622bc0f | |
| parent | e861e58a443a7a083378227c6d1a1e47b5ea4b1d [diff] |
Pass the device's API level to device test_config. We need to mark some tests as broken or unsupported based on what device they are running on, as opposed to just what they were built for. Change-Id: I4818aa23d5af6f47f02d3bee5a22d299088e5562
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.
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.
The NDK consists of three parts: host binaries, target prebuilts, and others (build system, docs, samples, tests).
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.ndk-depends and ndk-stack should probably go in prebuilt/ to avoid collisions between host variants.platforms/android-N/arch-$ARCH_NAME/ contains headers and libraries for each API level.--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.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/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):
Mac OS X also requires Xcode.
$ python checkbuild.py --no-package
$ python checkbuild.py --system windows
The simplest way to package an NDK on Linux is to just omit the --no-package flag when running checkbuild.py. 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/package-release.sh directly. This process will be improved in a future commit.
Running the NDK tests requires a complete NDK package (see previous steps). The full test suite includes tests which run on a device or emulator, so you'll need to have adb in your path and ANDROID_SERIAL set if more than one device/emulator is connected. With that package:
$ tar xf android-ndk-$BUILD_NUM-$HOST_TAG.tar.bz2 $ cd android-ndk-$BUILD_NUM $ export NDK=`pwd` $ python tests/run-all.py --abi $ABI_TO_TEST