path: root/docs
diff options
authorYann E. MORIN" <>2007-07-17 21:44:33 (GMT)
committerYann E. MORIN" <>2007-07-17 21:44:33 (GMT)
commitd5db172ef497472211ba081b70b2c8aad8ccbd89 (patch)
tree7841e59e928b43995024aaac3e5f3d66bbc253cd /docs
parent3f4ac101f2b4392089e68b9307a7773a97d0ce6d (diff)
Revisit the extract-config way of working: ct-ng is the sole entry point to crosstool-NG, and ct-ng.extrac-config no longer exists. You now have to call "ct-ng extractconfig </path/to/your/build.log" instead.
Diffstat (limited to 'docs')
1 files changed, 16 insertions, 0 deletions
diff --git a/docs/overview.txt b/docs/overview.txt
index 9b30589..1f936c2 100644
--- a/docs/overview.txt
+++ b/docs/overview.txt
@@ -165,6 +165,22 @@ CT_BROKEN:
brave enough, you can try and debug them. They are hidden behind CT_BROKEN,
which itself is hiddent behind EXPERIMENTAL.
+Re-building an existing toolchain |
+If you have an existing toolchain, you can re-use the options used to build it
+to create a new toolchain. That needs a very little bit of effort on your side
+but is quite easy. The options to build a toolchain are saved in the build log
+file that is saved within the toolchain. crosstool-NG can extract those options
+to recreate a new configuration:
+ ct-ng extractconfig </path/to/your/build.log
+will extract those options, prompt you for the new ones, which you can later
+edit with menuconfig.
+Of course, if your build log was compressed, you'd have to use something like:
+ bzcat /path/to/your/build.log.bz2 |ct-ng extractconfig
Running crosstool-NG /