Lines Matching refs:directory

1 This directory contains a number of shell scripts, which we will
45 First, a small description of the NDK's overall directory structure:
84 these sources, that will be copied under this directory.
91 from these sources, that will be copied under this directory.
96 This directory doesn't contain sources at all, only an Android.mk. The
103 This directory contains a few headers used to use the native system Android C++
106 dev-script described later, but it never placed in this directory.
111 This directory contains the sources of the libthread\_db implementation that is
124 This directory contains platform-specific files. The reason why it it is
145 Android 1.6. The platforms/android-4 directory only contains files that are
198 Not to be confused with $DEVNDK/platforms/, this directory is not part of the
199 NDK git directory (and is specifically listed in $NDK/.gitignore) but of its final
207 Moreover, the directory is organized slightly differently, i.e. as toolchain
242 The toolchains binaries are typically placed under the directory
249 First you will need to build a proper "sysroot" directory before being able to
252 A sysroot is a directory containing system headers and libraries that the
265 toolchain sources root directory, a destination NDK installation directory to
269 current NDK directory (which can be handy if you want to later use them to
323 script require that you generate a fully populated $NDK/platforms/ directory
339 directory when `ndk-build` is called.
405 to do this, where <path> points to a directory that will store compressed
450 You need to have a directory containing prebuilt tarballs, as described in the
481 Finally, --prebuilt-dir=<path> must point to the directory that contains the
488 The $NDK/tests directory contains a number of NDK unit-tests that can be used to
497 This will uncompress the NDK archive in a temporary directory, then run all the
498 tests with it. When all tests have run, the temporary directory is removed
506 suite present under $NDK/tests/, not the one in the remote NDK directory.
509 directory. This can only work if you have generated or unpacked all prebuilt