Lines Matching refs:NDK
2 call the "dev-scripts", that are only used to develop the NDK
15 - packaging final NDK release tarballs, including adding samples
16 and documentation which normally live in $NDK/../development/ndk
25 First, a small description of the NDK's overall directory structure:
27 $NDK/build/core
28 Contains the main NDK build system used when 'ndk-build'.
32 $NDK/build/tools
36 $NDK/sources/host-tools/
38 compiled to generate useful host programs for the final NDK
39 installation. For example, $NDK/sources/host-tools/ndk-stack/
42 $NDK/sources/cxx-stl/
47 $NDK/sources/cxx-stl/gabi++/
53 $NDK/sources/cxx-stl/stlport/
58 $NDK/sources/cxx-stl/llvm-libc++/
64 $NDK/sources/cxx-stl/gnu-libstdc++/
70 $NDK/sources/cxx-stl/system/
77 $NDK/sources/android/libthread_db/
86 $NDK/sources/
87 The rest of $NDK/sources/ is used to store the sources of helper
89 helper library is under $NDK/sources/android/cpu-features/
91 $DEVNDK a.k.a $NDK/../development/ndk
93 it is separate from $NDK is because it is not primarly developed in
98 - all $NDK development happens in the public AOSP repository ndk.git
121 Contains all system headers exposed by the NDK for a given platform.
135 Before NDK r7, this also contains prebuilt system shared libraries that
140 Contains, for each system shared library exposed by the NDK, two
147 These files were introduced in NDK r7 and are used to generate "shell"
163 $NDK/platforms/
165 part of the NDK git directory (and is spefically listed in $NDK/.gitignore)
170 $NDK/platforms/android-$PLATFORM will contain _all_ the files that
177 $NDK/platforms/android-$PLATFORM/arch-$ARCH/usr/include
178 $NDK/platforms/android-$PLATFORM/arch-$ARCH/usr/lib
185 $TOOLCHAIN_PREFIX-gcc --with-sysroot=$NDK/platforms/android-5/arch-arm
189 The dev-script 'gen-platforms.sh' is used to populate $NDK/platforms.
205 binaries are never distributed as part of official NDK releases.
208 $NDK/../prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/, which is
214 This shall always be used to official NDK Linux releases.
222 system supported by the NDK.
228 The NDK toolchain sources are located under the toolchain/ directly
242 need to be slightly patched for use with the NDK.
244 All patches are located under $NDK/build/tools/toolchain-patches/
250 $NDK/build/tools/download-toolchain-sources.sh /tmp/ndk-$USER/src
266 $NDK/build/tools/download-toolchain-sources.sh \
284 $NDK/toolchains/$NAME/prebuilt/$SYSTEM, where $NAME is the toolchain name's
300 $NDK/build/tools/gen-platforms.sh --minimal
302 This will populate $NDK/platforms/ with just the files necessary to rebuild the
307 to the toolchain sources root directory, a destination NDK installation
311 current NDK directory (which can be handy if you want to later use them to
314 $NDK/build/tools/build-gcc.sh /tmp/ndk-$USER/src $NDK arm-linux-androideabi-4.8
315 $NDK/build/tools/build-gcc.sh /tmp/ndk-$USER/src $NDK x86-4.8
332 $NDK/build/tools/build-gcc.sh --mingw \
333 /tmp/ndk-$USER/src $NDK arm-linux-androideabi-4.8
335 $NDK/build/tools/build-gcc.sh --mingw \
336 /tmp/ndk-$USER/src $NDK x86-4.8
338 The corresponding binaries are installed under $NDK/toolchains/$NAME/prebuilt/windows
357 A final NDK installation comes with a lot of various target-specific prebuilt
364 require that you generate a fully populated $NDK/platforms/ directory first. To do
367 $NDK/gen-platforms.sh
382 The prebuilt binary is placed under $NDK/toolchains/$NAME/prebuilt/gdbserver
383 in the final NDK installation. You can generate with 'build-gdbserver.sh' and
386 $NDK/build/tools/build-gcc.sh /tmp/ndk-$USER/src $NDK arm-linux-androideabi-4.8
387 $NDK/build/tools/build-gcc.sh /tmp/ndk-$USER/src $NDK x86-4.8
394 provided under $NDK/sources/cxx-stl/. Several dev-scripts are provided to
396 (e.g. the GAbi++ binaries will go to $NDK/sources/cxx-stl/gabi++/libs/)
402 the NDK, e.g. armeabi, armeabi-v7a, x86 and mips. You can restrict them using
410 $NDK/build/tools/build-cxx-stl.sh --stl=gabi++
411 $NDK/build/tools/build-cxx-stl.sh --stl=stlport
412 $NDK/build/tools/build-cxx-stl.sh --stl=libc++
413 $NDK/build/tools/build-gnu-libstdc++.sh /tmp/ndk-$USER/src
424 NDK installation. Their sources are typically installed under
425 $NDK/sources/host-tools/
435 helper host program. See docs/NDK-STACK.html for a usage description.
438 $NDK/build/tools/build-ndk-stack.sh
459 $NDK/build/tools/build-cxx-stl.sh --stl=gabi++ --package-dir=/tmp/ndk-$USER/prebuilt/
461 In NDK r7, this will actually create three tarballs (one per supported ABI),
470 of an existing NDK install tree.
474 $NDK/build/tools/build-cxx-stl.sh --stl=stlport --package-dir=/tmp/ndk-$USER/prebuilt
486 $NDK/build/tools/rebuild-all-prebuilt.sh \
506 For the record, with NDK r7, the list was:
509 VI. Packaging NDK releases:
512 Use the 'package-release.sh' dev-script to generate full NDK release packages.
513 These contain everything needed by a typical NDK user, including:
522 $NDK/build/tools/package-release.sh \
529 generated NDK archive. More specifically, the archive file name will be
543 By default, i.e. without the option, the scripts tries to build NDK archives
559 The $NDK/tests directory contains a number of NDK unit-tests that can be
560 used to verify that the generated NDK packages or the working NDK tree still
563 If you have an NDK package archive, you can run the following to run the
566 $NDK/tests/run-tests.sh --package=<ndk-archive>
568 This will uncompress the NDK archive in a temporary directory, then run all
572 You can also point to an existing NDK installation with --ndk=<path>, as in:
574 $NDK/tests/run-tests.sh --ndk=<path>
576 Where <path> points to another NDK installation. The script will run the
577 test suite present under $NDK/tests/, not the one in the remote NDK directory.
579 If you don't use any option, the test suite will be run with the current NDK
588 - 'build tests' are used to test the building capabilities of the NDK.
589 I.e. the tests will only use them to check that the NDK build system
602 Whenever you add a feature to the NDK, or fix a bug, it is recommended to
603 add a unit test to check the feature or the fix. Use $NDK/tests/build for
604 build tests, and $NDK/tests/device for device tests.