From 5ff9c06cf35fdee01776c15049aa49ac53159816 Mon Sep 17 00:00:00 2001 From: "Yann E. MORIN\"" Date: Wed, 20 Feb 2008 22:48:35 +0000 Subject: - Rewrite some parts of history: some sentences could have been considered rude, which was not my intention. - Fix a few typoes at the same time. diff --git a/docs/overview.txt b/docs/overview.txt index 1ac8552..1bff0c1 100644 --- a/docs/overview.txt +++ b/docs/overview.txt @@ -66,24 +66,16 @@ purpose setup files to be used to configure crosstool. This is available at http://www.kegel.com/crosstool, and the subversion repository is hosted on google at http://code.google.com/p/crosstool/. -At the time of writing, crosstool supports building with only one C library, -namely glibc, and one C compiler, gcc; it is crippled with historical support -for legacy components, and is some kind of a mess to upgrade. Also, submitted -patches take a loooong time before they are integrated into mainline. - I once managed to add support for uClibc-based toolchains, but it did not make -into mainline, mostly because I don't have time to port the patch forward to +into mainline, mostly because I didn't have time to port the patch forward to the new versions, due in part to the big effort it was taking. So I decided to clean up crosstool in the state it was, re-order the things -in place, and add appropriate support for what I needed, that is uClibc -support. That was a disaster, as inclusion into mainline is slow as hell, -and the changes were so numerous. - -The only option left to me was rewrite crosstool from scratch. I decided to go -this way, and name the new implementation crosstool-NG, standing for crosstool -Next Generation, as many other comunity projects do, and as a wink at the TV -series "Star Trek: The Next Generation". ;-) +in place, add appropriate support for what I needed, that is uClibc support +and a menu-driven configuration, named the new implementation crosstool-NG, +(standing for crosstool Next Generation, as many other comunity projects do, +and as a wink at the TV series "Star Trek: The Next Generation" ;-) ) and +made it available to the community, in case it was of interest to any one. ___________________________ @@ -190,7 +182,7 @@ CT_LOCAL_TARBALLS_DIR: CT_PREFIX_DIR: This is where the toolchain will be installed in (and for now, where it - will run from). Common use it to add the target tuple in the directory + will run from). Common use is to add the target tuple in the directory path, such as (see above): /opt/x-tools/${CT_TARGET} @@ -447,7 +439,7 @@ traditional command. ct-ng loads sub- Makefiles from the library directory $(CT_LIB_DIR), as set up at configuration time with ./configure. -ct-ng also search for config files, sub-tools, samples, scripts and patches in +ct-ng also searches for config files, sub-tools, samples, scripts and patches in that library directory. Because of a stupid make behavior/bug I was unable to track down, implicit make -- cgit v0.10.2-6-g49f6