Re-order and rework a bit docs/overview.txt. Plus a typo fix.

This commit is contained in:
Yann E. MORIN" 2007-07-17 21:49:43 +00:00
parent d5db172ef4
commit 8c23854de2

View File

@ -90,8 +90,14 @@ ____________________________
Configuring crosstool-NG /
_________________________/
crosstool-NG is configured the same way you configure your Linux kernel: by
using a curses-based menu. It is assumed you now how to handle this.
crosstool-NG is configured by a configurator presenting a menu-stuctured set of
options. These options let you specify the way you want your toolchain built,
where you want it installed, what architecture and specific processor it
will support, the version of the components you want to use, etc... The
value for those options are then stored in a configuration file.
The configurator works the same way you configure your Linux kernel.It is
assumed you now how to handle this.
To enter the menu, type:
ct-ng menuconfig
@ -126,13 +132,15 @@ Interesting config options |
---------------------------*
CT_LOCAL_TARBALLS_DIR:
If you already have sone tarballs in a direcotry, enter it here. That will
If you already have some tarballs in a direcotry, enter it here. That will
speed up the retrieving phase, where crosstool-NG would otherwise download
those tarballs.
CT_PREFIX_DIR:
This is where the toolchain will be installed in (and for now, where it
will run from).
will run from). Common use it to add the target triplet in the directory
path, such as (see above):
/opt/x-tools/${CT_TARGET}
CT_TARGET_VENDOR:
An identifier for your toolchain, will take place in the vendor part of the
@ -186,12 +194,6 @@ ________________________
Running crosstool-NG /
_____________________/
crosstool-NG is configured by a configurator presenting a menu-stuctured set of
options. These options let you specify the way you want your toolchain built,
where you want it installed, what architecture and specific processor it
will support, the version of the components you want to use, etc... The
value for those options are then stored in a configuration file.
To build the toolchain, simply type:
ct-ng build