diff options
| author | Andrew Hsieh <andrewhsieh@google.com> | 2014-12-17 18:35:18 +0800 |
|---|---|---|
| committer | Andrew Hsieh <andrewhsieh@google.com> | 2014-12-18 10:47:44 +0800 |
| commit | e5e7599ff9e946f3d47c6b3150d7265c1e2dab38 (patch) | |
| tree | ba868aeb9e73d3d894a18e3698775580d44d95d7 /build/tools/DEV-SCRIPTS-USAGE.TXT | |
| parent | cde0cb89ada253e9f7f4194de6f7f6af138b7e09 (diff) | |
| download | ndk-e5e7599ff9e946f3d47c6b3150d7265c1e2dab38.tar.gz | |
Remove GCC 4.6
Change-Id: I840e7a2183e956e27e5dd93357ef2a2dd49fd40b
Diffstat (limited to 'build/tools/DEV-SCRIPTS-USAGE.TXT')
| -rw-r--r-- | build/tools/DEV-SCRIPTS-USAGE.TXT | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/build/tools/DEV-SCRIPTS-USAGE.TXT b/build/tools/DEV-SCRIPTS-USAGE.TXT index 8ad8d6f0e..95a29c9e6 100644 --- a/build/tools/DEV-SCRIPTS-USAGE.TXT +++ b/build/tools/DEV-SCRIPTS-USAGE.TXT @@ -282,7 +282,7 @@ to verify that the patches apply cleanly. The toolchains binaries are typically placed under the directory $NDK/toolchains/$NAME/prebuilt/$SYSTEM, where $NAME is the toolchain name's -full name (e.g. arm-linux-androideabi-4.6), and $SYSTEM is the name of the +full name (e.g. arm-linux-androideabi-4.8), and $SYSTEM is the name of the host system it is meant to run on (e.g. 'linux-x86', 'windows' or 'darwin-x86') @@ -311,8 +311,8 @@ For example, to rebuild the arm and x86 prebuilt toolchain binaries in the current NDK directory (which can be handy if you want to later use them to rebuild other target prebuilts or run tests), do: - $NDK/build/tools/build-gcc.sh /tmp/ndk-$USER/src $NDK arm-linux-androideabi-4.6 - $NDK/build/tools/build-gcc.sh /tmp/ndk-$USER/src $NDK x86-4.6 + $NDK/build/tools/build-gcc.sh /tmp/ndk-$USER/src $NDK arm-linux-androideabi-4.8 + $NDK/build/tools/build-gcc.sh /tmp/ndk-$USER/src $NDK x86-4.8 Here, we assume you downloaded the toolchain sources in /tmp/ndk-$USER/src as described in the previous section. @@ -330,10 +330,10 @@ cross-toolchain (install it with "apt-get install mingw32" on Ubuntu). To do so use the "--mingw" option, as in: $NDK/build/tools/build-gcc.sh --mingw \ - /tmp/ndk-$USER/src $NDK arm-linux-androideabi-4.6 + /tmp/ndk-$USER/src $NDK arm-linux-androideabi-4.8 $NDK/build/tools/build-gcc.sh --mingw \ - /tmp/ndk-$USER/src $NDK x86-4.6 + /tmp/ndk-$USER/src $NDK x86-4.8 The corresponding binaries are installed under $NDK/toolchains/$NAME/prebuilt/windows Note that these are native Windows programs, not Cygwin ones. @@ -383,8 +383,8 @@ The prebuilt binary is placed under $NDK/toolchains/$NAME/prebuilt/gdbserver in the final NDK installation. You can generate with 'build-gdbserver.sh' and takes the same parameters than 'build-gcc.sh'. So one can do: - $NDK/build/tools/build-gcc.sh /tmp/ndk-$USER/src $NDK arm-linux-androideabi-4.6 - $NDK/build/tools/build-gcc.sh /tmp/ndk-$USER/src $NDK x86-4.6 + $NDK/build/tools/build-gcc.sh /tmp/ndk-$USER/src $NDK arm-linux-androideabi-4.8 + $NDK/build/tools/build-gcc.sh /tmp/ndk-$USER/src $NDK x86-4.8 III.3. Generating C++ runtime prebuilt binaries: |