Merge the build system to trunk: ct-ng is now installable:

 - ./configure --prefix=/some/place
 - make
 - make install
 - export PATH="${PATH}:/some/place/bin"
 - ct-ng <action>

1 files changed, 9 insertions, 9 deletions

diff --git a/docs/overview.txt b/docs/overview.txt
index cd5c9f7..14dc0a2 100644
--- a/docs/overview.txt
+++ b/docs/overview.txt
@@ -110,9 +110,9 @@ CT_TARGET:
     /opt/x-tools/${CT_TARGET}
 
 CT_TOP_DIR:
-  The top directory where crosstool-NG sits. You shouldn't need it in most
-  cases. There is one case where you may need it: if you have local patches
-  and you store them in your copy of crosstool-NG, you can refer to them
+  The top directory where crosstool-NG is running. You shouldn't need it in
+  most cases. There is one case where you may need it: if you have local
+  patches and you store them in your running directory, you can refer to them
   by using CT_TOP_DIR, such as:
     ${CT_TOP_DIR}/patches.myproject
 
@@ -274,13 +274,13 @@ Makefile-based.
 Makefile front-end |
 -------------------*
 
-The Makefile defines a set of rules to call each action. You can get the
-list, along with some terse description, by typing "make help" in your
-favourite command line.
+To Be Written later...
 
-The Makefile sets the version variable from the version file in ${CT_TOP_DIR}
-which is then available to others in the CT_VERSION environment variable.
+Kconfig parser |
+---------------*
 
 The kconfig language is a hacked version, vampirised from the toybox project
-by Rob LANDLEY (http://www.landley.net/code/toybox/), adapted to my needs.
+by Rob LANDLEY (http://www.landley.net/code/toybox/), itself coming from the
+Linux kernel (http://www.linux.org/ http://www.kernel.org/), and (heavily)
+adapted to my needs.