path: root/docs/3 - Configuring a toolchain.txt
diff options
authorAlexey Neyman <>2017-01-24 22:52:23 (GMT)
committerGitHub <>2017-01-24 22:52:23 (GMT)
commit027a75cbf0e8361160485b5869f3a554cf44977c (patch)
tree3e0b221224d422a5f3fca2ff1204e27b6975b633 /docs/3 - Configuring a toolchain.txt
parent9061763a73c38032c1d889256f27929368381069 (diff)
parent83d78d33d3086b41dfd5690a41150db14b054084 (diff)
Merge pull request #549 from stilor/backend-obsolete
Declare BACKEND obsolete.
Diffstat (limited to 'docs/3 - Configuring a toolchain.txt')
-rw-r--r--docs/3 - Configuring a toolchain.txt16
1 files changed, 0 insertions, 16 deletions
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:
-(case is not sensitive, you can say Y).