1.1 --- a/docs/overview.txt	Thu Feb 11 21:28:10 2010 +0100
     1.2 +++ b/docs/overview.txt	Fri Mar 05 09:19:56 2010 +0100
     1.3 @@ -21,6 +21,7 @@
     1.4  Configuring crosstool-NG
     1.5    Interesting config options
     1.6    Re-building an existing toolchain
     1.7 +  Using as a backend for a build-system
     1.8  Running crosstool-NG
     1.9    Stopping and restarting a build
    1.10    Testing all toolchains at once
    1.11 @@ -350,6 +351,21 @@
    1.12  Then, you can review and change the configuration by running:
    1.13    ct-ng menuconfig
    1.14  
    1.15 +Using as a backend for a build-system |
    1.16 +--------------------------------------+
    1.17 +
    1.18 +Crosstool-NG can be used as a backend for an automated build-system. In this
    1.19 +case, some components that are expected to run on the target (eg. the native
    1.20 +gdb, ltrace, DUMA...) are not available in the menuconfig, and they are not
    1.21 +build either, as it is considered the responsibility of the build-system to
    1.22 +build its own versions of those tools.
    1.23 +
    1.24 +If you want to use crosstool-NG as a backend to generate your toolchains for
    1.25 +your build-system, you have to set and export this environment variable:
    1.26 +  CT_IS_A_BACKEND=y
    1.27 +
    1.28 +(case is not sensitive, you can say Y).
    1.29 +
    1.30  
    1.31  ________________________
    1.32                         /