# HG changeset patch
# User "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
# Date 1184002545 0
# Node ID 15f44768d3f702eb9085631689f047d5b2697b7c
# Parent  7055198d062d5596b112a67b60238d038de9baa7
Update man page to explictly point to overview.txt.
In overview.txt, document usage of the populate script.

diff -r 7055198d062d -r 15f44768d3f7 docs/ct-ng.1.in
--- a/docs/ct-ng.1.in	Mon Jul 09 16:34:44 2007 +0000
+++ b/docs/ct-ng.1.in	Mon Jul 09 17:35:45 2007 +0000
@@ -159,12 +159,16 @@
 (see section titled
 .BR "SEE ALSO" )
 scripts to be more easily maintainable, added the Kconfig configurator, some
-patches.
+patches, support for linux headers installation, and support for uClibc-based
+toolchains.
 
 Please consult the file
 .I @@CT_DOCDIR@@/CREDITS
 for a list of contributors.
 ."
 .SH SEE ALSO
+You can find more in-depth documentation in
+.IR @@CT_DOCDIR@@/overview.txt .
+
 Please have a look at the
 .URL "http://www.kegel.com/crosstool" "original crosstool" " by Daniel KEGEL"
diff -r 7055198d062d -r 15f44768d3f7 docs/overview.txt
--- a/docs/overview.txt	Mon Jul 09 16:34:44 2007 +0000
+++ b/docs/overview.txt	Mon Jul 09 17:35:45 2007 +0000
@@ -206,6 +206,35 @@
 You can test-build all samples; simply call:
   ct-ng regtest
 
+_______________________
+                      /
+Using the toolchain  /
+____________________/
+
+Using the toolchain is as simple as adding the toolchain's bin directory in
+your PATH, such as:
+  export PATH="${PATH}:/your/toolchain/path/bin"
+
+and then using the target triplet to tell the build systems to use your
+toolchain:
+  ./configure --target=your-target-triplet
+  make CC=your-target-triplet-gcc
+  make CROSS_COMPILE=your-target-triplet-
+  and so on...
+
+When your root directory is ready, it is still missing some important bits: the
+toolchain's libraries. To populate your root directory with those libs, just
+run:
+  your-target-triplet-populate -s /your/root -d /your/root-populated
+
+This will copy /your/root into /your/root-populated, and put the needed and only
+the needed libraries there. Thus you don't polute /your/root with any cruft that
+would no longer be needed should you have to remove stuff. /your/root always
+contains only those things you install in it.
+
+You can then use /your/root-populated to build up your file system image, a
+tarball, or to NFS-mount it from your target, or whatever you need.
+
 ___________________
                   /
 Toolchain types  /