Remove download-toolchain-sources.sh from the docs.

I haven't cleaned up the scripts on the assumption that they're all
going the way of the dodo anyway.

Change-Id: Iaee6bc69887d7f50cc5c4fc983c90b1607259115

README.md

@@ -107,29 +107,14 @@ Host/Target prebuilts
 ### On Linux:
 
 ```bash
-$ export AOSP=/absolute/path/to/aosp
-$ export NDK=$AOSP/ndk
-$ export PREBUILT_PATH=/absolute/path/to/packaged/output
-$ cd $NDK
-$ build/tools/dev-cleanup.sh
-$ build/tools/download-toolchain-sources.sh /tmp/ndk-$USER/src
-$ build/tools/rebuild-all-prebuilt.sh /tmp/ndk-$USER/src \
-    --package-dir=$PREBUILT_PATH --also-64 --systems=linux-x86,windows
+$ checkbuild.sh --also-64 --systems=linux-x86,windows
 ```
 
 ### On MacOS X:
 
 ```bash
-$ export AOSP=/absolute/path/to/aosp
-$ export NDK=$AOSP/ndk
-$ export PREBUILT_PATH=/absolute/path/to/packaged/output
-$ cd $NDK
-$ build/tools/dev-cleanup.sh
-$ build/tools/build-host-prebuilts.sh --ndk-dir=$NDK \
-    --package-dir=$PREBUILT_PATH --systems=darwin-x86 /tmp/ndk-$USER/src \
-    --try-64
-$ build/tools/build-host-prebuilts.sh --ndk-dir=$NDK \
-    --package-dir=$PREBUILT_PATH --systems=darwin-x86 /tmp/ndk-$USER/src
+$ checkbuild.sh --systems=darwin-x86 --try-64
+$ checkbuild.sh --systems=darwin-x86
 ```
 
 Packaging
@@ -149,9 +134,6 @@ Best Practices for Incremental Builds
 * Do not run `build/tools/dev-cleanup.sh` which erases all prebuilts.
 * Remove the individual prebuilt directory if new build deletes files. This is
   rare.
-* Avoid running `build/tools/download-toolchain-sources.sh` during development
-  because the size of toolchains repo is ~8GB. Changes made to individual
-  projects can be cherry-picked to `/tmp/ndk-$USER/src`.
 * Package NDK from prebuilt tarballs in `$PREBUILT_PATH`. It runs
   `build/tools/build-docs.sh` which produces no tarball in `$PREBUILT_PATH`.
 * Unpack and compare against the previous package.

build/tools/DEV-SCRIPTS-USAGE.TXT

@@ -220,23 +220,11 @@ system supported by the NDK.
 II.1 Getting the toolchain sources:
 - - - - - - - - - - - - - - - - - -
 
-The NDK toolchain sources are located under the toolchain/ directly
-from the top of the public AOSP repositories. There are actually several
-git repositories of interest here:
-
-    binutils/
-    build/
-    gcc/
-    gdb/
-    gold/
-    gmp/
-    mpfr/
-
-The AOSP toolchain/ repository contains sources corresponding to toolchains
-that are used to build the Android platform tree.
+The AOSP toolchain/ repository contains the source for the toolchains
+used to build the Android platform and in the NDK.
 
 The master-ndk branch of AOSP contains an already checked out and patched
-version of the toolchain repository at toolchain/. The process of using
+version of the toolchain repository at toolchain/. The old process of using
 download-toolchain-sources.sh is now obsolete.
 
 The toolchains binaries are typically placed under the directory
@@ -273,8 +261,8 @@ rebuild other target prebuilts or run tests), do:
    $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.
+Here, we assume you're using the master-ndk branch as described in the previous
+section.
 
 This operation can take some time. The script automatically performs a parallel
 build to speed up the build on multi-core machine (use the -j<number> option to
@@ -434,16 +422,8 @@ Similarly, to rebuild the STLport binaries and package them:
 
 A dev-script is provided to rebuild _and_ package all prebuilts. It is called
 'rebuild-all-prebuilt.sh'. Note that by default, it will automatically
-invoke 'download-toolchain-sources.sh', and place the prebuilt tarballs
-under /tmp/ndk-$USER/prebuilt-$DATE, where $DATE is the current date in
-ISO format (e.g. 20110915 for the 15th of September of 2011).
-
-If you have already downloaded the toolchain sources, use the
---toolchain-src-dir=<path> option to save a few minutes to your rebuild,
-as in:
-
-  $NDK/build/tools/rebuild-all-prebuilt.sh \
-        --toolchain-src-dir=/tmp/ndk-$USER/src
+place the prebuilt tarballs under /tmp/ndk-$USER/prebuilt-$DATE, where $DATE
+is the current date in ISO order.
 
 By default, this only rebuilds the host prebuilds for the current host
 system. You can use --mingw to force the generation of Windows binaries on

docs/Programmers_Guide/html/md_4__additional__info__l_i_c_e_n_s_e_s.html

@@ -54,7 +54,7 @@ $(document).ready(function(){initNavTree('md_4__additional__info__l_i_c_e_n_s_e_
 </div><!--header-->
 <div class="contents">
 <div class="textblock"><p>The content of the Android NDK is covered by various open-source licenses. See the copyright disclaimers in each respective file for details.</p>
-<p>Note that the public Android NDK release packages also contain prebuilt binaries for the compiler, linker, archiver, etc... The source code for the toolchain is available at android.googlesource.com (you can use the script under build/tools/download-toolchain-sources.sh to download it automatically).</p>
+<p>Note that the public Android NDK release packages also contain prebuilt binaries for the compiler, linker, archiver, etc... The source code for the toolchain is available at android.googlesource.com (see the README.md in <code>ndk/</code>).</p>
 <p>The prebuilt binaries are covered by either the GNU General Public License (GPL), or the GNU Lesser General Public License (LGPL). For details, see the files COPYING and COPYING.LIB under <code>build/prebuilt/&lt;system&gt;/&lt;toolchain&gt;</code>. </p>
 </div></div><!-- contents -->
 </div><!-- doc-content -->