docs/overview.txt
changeset 227 15f44768d3f7
parent 203 73b023845581
child 246 372bc84bea36
     1.1 --- a/docs/overview.txt	Wed Jul 04 17:37:48 2007 +0000
     1.2 +++ b/docs/overview.txt	Mon Jul 09 17:35:45 2007 +0000
     1.3 @@ -206,6 +206,35 @@
     1.4  You can test-build all samples; simply call:
     1.5    ct-ng regtest
     1.6  
     1.7 +_______________________
     1.8 +                      /
     1.9 +Using the toolchain  /
    1.10 +____________________/
    1.11 +
    1.12 +Using the toolchain is as simple as adding the toolchain's bin directory in
    1.13 +your PATH, such as:
    1.14 +  export PATH="${PATH}:/your/toolchain/path/bin"
    1.15 +
    1.16 +and then using the target triplet to tell the build systems to use your
    1.17 +toolchain:
    1.18 +  ./configure --target=your-target-triplet
    1.19 +  make CC=your-target-triplet-gcc
    1.20 +  make CROSS_COMPILE=your-target-triplet-
    1.21 +  and so on...
    1.22 +
    1.23 +When your root directory is ready, it is still missing some important bits: the
    1.24 +toolchain's libraries. To populate your root directory with those libs, just
    1.25 +run:
    1.26 +  your-target-triplet-populate -s /your/root -d /your/root-populated
    1.27 +
    1.28 +This will copy /your/root into /your/root-populated, and put the needed and only
    1.29 +the needed libraries there. Thus you don't polute /your/root with any cruft that
    1.30 +would no longer be needed should you have to remove stuff. /your/root always
    1.31 +contains only those things you install in it.
    1.32 +
    1.33 +You can then use /your/root-populated to build up your file system image, a
    1.34 +tarball, or to NFS-mount it from your target, or whatever you need.
    1.35 +
    1.36  ___________________
    1.37                    /
    1.38  Toolchain types  /