1.1 --- a/docs/overview.txt Mon Jul 02 17:47:17 2007 +0000
1.2 +++ b/docs/overview.txt Mon Jul 02 19:40:54 2007 +0000
1.3 @@ -1,5 +1,5 @@
1.4 File.........: overview.txt
1.5 -Content......: Overview of how ct-ng works.
1.6 +Content......: Overview of how crosstool-NG works.
1.7 Copyrigth....: (C) 2007 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
1.8 License......: Creative Commons Attribution Share Alike (CC-by-sa), v2.5
1.9
1.10 @@ -38,7 +38,7 @@
1.11 - they are proven if used by a wide community.
1.12
1.13 But once you want to get all the juice out of your specific hardware, you will
1.14 -want to build your own toolchain. This is where crosstool-ng comes into play.
1.15 +want to build your own toolchain. This is where crosstool-NG comes into play.
1.16
1.17 There are also a number of tools that builds toolchains for specific needs,
1.18 which is not really scalable. Examples are:
1.19 @@ -80,9 +80,9 @@
1.20 support.
1.21
1.22 The only option left to me was rewrite crosstool from scratch. I decided to go
1.23 -this way, and name the new implementation ct-ng, standing for crosstool Next
1.24 -Generation, as many other comunity projects do, and as a wink at the TV series
1.25 -"Star Trek: The Next Generation". ;-)
1.26 +this way, and name the new implementation crosstool-NG, standing for crosstool
1.27 +Next Generation, as many other comunity projects do, and as a wink at the TV
1.28 +series "Star Trek: The Next Generation". ;-)
1.29
1.30 ____________________________
1.31 /
1.32 @@ -126,7 +126,7 @@
1.33
1.34 CT_LOCAL_TARBALLS_DIR:
1.35 If you already have sone tarballs in a direcotry, enter it here. That will
1.36 - speed up the retrieving phase, where crosstool-ng would otherwise download
1.37 + speed up the retrieving phase, where crosstool-NG would otherwise download
1.38 those tarballs.
1.39
1.40 CT_PREFIX_DIR:
1.41 @@ -148,7 +148,7 @@
1.42 Running crosstool-NG /
1.43 _____________________/
1.44
1.45 -ct-ng is configured by a configurator presenting a menu-stuctured set of
1.46 +crosstool-NG is configured by a configurator presenting a menu-stuctured set of
1.47 options. These options let you specify the way you want your toolchain built,
1.48 where you want it installed, what architecture and specific processor it
1.49 will support, the version of the components you want to use, etc... The
1.50 @@ -235,29 +235,30 @@
1.51 one it is built on, and running again on this exact same machine. You have
1.52 to build such a toolchain when you want to use an updated component, such
1.53 as a newer gcc for example.
1.54 - ct-ng calls it "native".
1.55 + crosstool-NG calls it "native".
1.56
1.57 2) build == host != target
1.58 This is a classic cross-toolchain, which is expected to be run on the same
1.59 machine it is compiled on, and generate code to run on a second machine,
1.60 the target.
1.61 - ct-ng calls it "cross".
1.62 + crosstool-NG calls it "cross".
1.63
1.64 3) build != host == target
1.65 Such a toolchain is also a native toolchain, as it targets the same machine
1.66 as it runs on. But it is build on another machine. You want such a
1.67 toolchain when porting to a new architecture, or if the build machine is
1.68 much faster than the host machine.
1.69 - ct-ng calls it "cross-native".
1.70 + crosstool-NG calls it "cross-native".
1.71
1.72 4) build != host != target
1.73 This one is called a canadian-toolchain (*), and is tricky. The three
1.74 machines in play are different. You might want such a toolchain if you
1.75 have a fast build machine, but the users will use it on another machine,
1.76 and will produce code to run on a third machine.
1.77 - ct-ng calls it "canadian".
1.78 + crosstool-NG calls it "canadian".
1.79
1.80 -ct-ng can build all these kinds of toolchains (or is aiming at it, anyway!)
1.81 +crosstool-NG can build all these kinds of toolchains (or is aiming at it,
1.82 +anyway!)
1.83
1.84 (*) The term Canadian Cross came about because at the time that these issues
1.85 were all being hashed out, Canada had three national political parties.