commit | 12ad0bb9ef6b173a94071718bb849277994d042f | [log] [tgz] |
---|---|---|
author | Dan Albert <danalbert@google.com> | Wed Feb 21 15:03:28 2018 -0800 |
committer | Dan Albert <danalbert@google.com> | Wed Feb 21 15:30:53 2018 -0800 |
tree | 3a10d464f7caffecd915c0154db18f8e0bd38da9 | |
parent | 43fbf405ccb268ef2c22452887218db42b4e0192 [diff] |
Fix bug in ldflags_to_sanitizers.py. The Python tests were passing because we only tested the individual functions, not the program as a whole. The run_tests.py tests were passing because errors from $(shell) do not cause the build to fail; ndk-build just ended up parsing the error message and not finding any sanitizers. The asan-smoke test passed because A) I hadn't run `./run_tests.py --clean-device` to purge the old tests, so the libraries were still on the device and B) running the tests in the r17 branch had led to asan_device_setup running again, installing the libraries to the system partition once again. Test: nose2 build Test: ./run_tests.py --clean-device # After purging asan /system libs Bug: https://github.com/android-ndk/ndk/issues/540 Change-Id: I85a30cc198be4a0f39548271f56112835805ca76
The latest version of this document is available at https://android.googlesource.com/platform/ndk/+/master/README.md.
Note: This document is for developers of the NDK, not developers that use the NDK.
The NDK allows Android application developers to include native code in their Android application packages, compiled as JNI shared libraries.
Both Linux and Windows NDKs are built on Linux machines. Windows host binaries are cross-compiled with MinGW.
Building the NDK for Mac OS X requires at least 10.8.
The NDK components can be loosely grouped into host toolchains, target prebuilts, build systems, and support libraries.
toolchains/
contains GCC and Clang 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_TAG
contains build dependencies and additional tools.ndk-depends
, ndk-stack
and ndk-gdb
can also be found here.sysroot/usr/include
contains the headers for the NDK. See Unified Headers for more information.platforms/android-$VERSION/arch-$ARCH_NAME/
contains stub shared libraries and a few static libraries for each API level. See Platform APIs for more information.sources/cxx-stl/$STL
contains the headers and libraries for the various C++ STLs.prebuilt/android-$ARCH/gdbserver
contains gdbserver.build/
contains ndk-build, the NDK's home grown build system. Most of the implementation lives in build/core
.build/cmake
contains components for using the NDK with CMake (at present only a CMake toolchain file, but in the future it will contain CMake modules that CMake will load, obviating the need for a toolchain file).build/tools
contains make_standalone_toolchain.py
, but also contains legacy sripts that were used to build the NDK. Eventually, this should contain nothing but the standalone toolchain scripts.sources/android
and sources/third_party
contain modules that can be used in apps (gtest, cpufeatures, native_app_glue, etc) via $(call import-module,$MODULE)
.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
Linux dependencies are listed in the Dockerfile. You can use docker to build the NDK:
docker build -t ndk-dev infra/docker docker run -it -u $UID -v `realpath ..`:/src -w /src/ndk ndk-dev ./checkbuild.py
Building on Mac OS X has similar dependencies as Linux, but also requires Xcode.
Running tests requires that adb
is in your PATH
. This is provided as part of the Android SDK.
$ python checkbuild.py
$ python checkbuild.py --system windows # Or windows64.
checkbuild.py
will also build all of the NDK tests. This takes about four times as long as building the NDK itself, so pass --no-build-tests
to skip building the tests. They can be built later with python run_tests.py --rebuild
.
checkbuild.py
also accepts a variety of other options to speed up local builds, namely --arch
and --module
.
By default, checkbuild.py
will also package the NDK. To skip the packaging step, use the --no-package
flag. To avoid packaging an incomplete NDK, packaging will not be run if --module
was passed unless --force-package
was also provided.