path: root/docs/3 - Configuring a toolchain.txt
diff options
authorAlexey Neyman <>2017-01-20 07:27:13 (GMT)
committerAlexey Neyman <>2017-01-20 07:27:13 (GMT)
commit83d78d33d3086b41dfd5690a41150db14b054084 (patch)
treeea643be96dcf8186ce05f9f273c966adda76686d /docs/3 - Configuring a toolchain.txt
parentdc3f68c8a5501fd745d079d724da389ea05566f8 (diff)
Declare BACKEND obsolete.
Signed-off-by: Alexey Neyman <>
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).