1.1 --- a/docs/ct-ng.1.in	Mon Jul 09 16:34:44 2007 +0000
     1.2 +++ b/docs/ct-ng.1.in	Mon Jul 09 17:35:45 2007 +0000
     1.3 @@ -159,12 +159,16 @@
     1.4  (see section titled
     1.5  .BR "SEE ALSO" )
     1.6  scripts to be more easily maintainable, added the Kconfig configurator, some
     1.7 -patches.
     1.8 +patches, support for linux headers installation, and support for uClibc-based
     1.9 +toolchains.
    1.10  
    1.11  Please consult the file
    1.12  .I @@CT_DOCDIR@@/CREDITS
    1.13  for a list of contributors.
    1.14  ."
    1.15  .SH SEE ALSO
    1.16 +You can find more in-depth documentation in
    1.17 +.IR @@CT_DOCDIR@@/overview.txt .
    1.18 +
    1.19  Please have a look at the
    1.20  .URL "http://www.kegel.com/crosstool" "original crosstool" " by Daniel KEGEL"

     2.1 --- a/docs/overview.txt	Mon Jul 09 16:34:44 2007 +0000
     2.2 +++ b/docs/overview.txt	Mon Jul 09 17:35:45 2007 +0000
     2.3 @@ -206,6 +206,35 @@
     2.4  You can test-build all samples; simply call:
     2.5    ct-ng regtest
     2.6  
     2.7 +_______________________
     2.8 +                      /
     2.9 +Using the toolchain  /
    2.10 +____________________/
    2.11 +
    2.12 +Using the toolchain is as simple as adding the toolchain's bin directory in
    2.13 +your PATH, such as:
    2.14 +  export PATH="${PATH}:/your/toolchain/path/bin"
    2.15 +
    2.16 +and then using the target triplet to tell the build systems to use your
    2.17 +toolchain:
    2.18 +  ./configure --target=your-target-triplet
    2.19 +  make CC=your-target-triplet-gcc
    2.20 +  make CROSS_COMPILE=your-target-triplet-
    2.21 +  and so on...
    2.22 +
    2.23 +When your root directory is ready, it is still missing some important bits: the
    2.24 +toolchain's libraries. To populate your root directory with those libs, just
    2.25 +run:
    2.26 +  your-target-triplet-populate -s /your/root -d /your/root-populated
    2.27 +
    2.28 +This will copy /your/root into /your/root-populated, and put the needed and only
    2.29 +the needed libraries there. Thus you don't polute /your/root with any cruft that
    2.30 +would no longer be needed should you have to remove stuff. /your/root always
    2.31 +contains only those things you install in it.
    2.32 +
    2.33 +You can then use /your/root-populated to build up your file system image, a
    2.34 +tarball, or to NFS-mount it from your target, or whatever you need.
    2.35 +
    2.36  ___________________
    2.37                    /
    2.38  Toolchain types  /