summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/0 - Table of content.txt1
-rw-r--r--docs/3 - Configuring a toolchain.txt16
2 files changed, 0 insertions, 17 deletions
diff --git a/docs/0 - Table of content.txt b/docs/0 - Table of content.txt
index 13e298b..27b25d9 100644
--- a/docs/0 - Table of content.txt
+++ b/docs/0 - Table of content.txt
@@ -21,7 +21,6 @@ _________________/
3- Configuring a toolchain
- Interesting config options
- Re-building an existing toolchain
- - Using as a backend for a build-system
4- Building the toolchain
- Stopping and restarting a build
diff --git a/docs/3 - Configuring a toolchain.txt b/docs/3 - Configuring a toolchain.txt
index b9cbace..8671d3f 100644
--- a/docs/3 - Configuring a toolchain.txt
+++ b/docs/3 - Configuring a toolchain.txt
@@ -115,19 +115,3 @@ toolchain with this configuration, just redirect the output to the
Then, you can review and change the configuration by running:
ct-ng menuconfig
-
-
-Using as a backend for a build-system |
---------------------------------------+
-
-Crosstool-NG can be used as a backend for an automated build-system. In this
-case, some components that are expected to run on the target (eg. the native
-gdb, ltrace, DUMA...) are not available in the menuconfig, and they are not
-build either, as it is considered the responsibility of the build-system to
-build its own versions of those tools.
-
-If you want to use crosstool-NG as a backend to generate your toolchains for
-your build-system, you have to set and export this environment variable:
- CT_IS_A_BACKEND=y
-
-(case is not sensitive, you can say Y).