path: root/docs
diff options
authorYann E. MORIN" <>2008-10-01 18:10:40 (GMT)
committerYann E. MORIN" <>2008-10-01 18:10:40 (GMT)
commit16c6cc994fe1325535caa16dab5590c5a4cf2246 (patch)
tree13eb0c745c1997d1833326ae6d1ab03554b2d8e3 /docs
parentc7f3478a1056b41fa18101fa3dc4f67aca89fd0d (diff)
Save the toolchain configuration to its own file, as an auto-extracting shell script:
- get rid of the 'extractconfig' action, it was cumbersome to use, and badly documented, - introduce a skeleton for the config script, - update auto-completion, - document the config script. /trunk/kconfig/ | 9 2 7 0 ++------- /trunk/scripts/ | 6 5 1 0 +++++- /trunk/docs/overview.txt | 21 9 12 0 +++++++++------------ /trunk/tools/ | 8 8 0 0 ++++++++ /trunk/ct-ng.comp | 2 1 1 0 +- 5 files changed, 25 insertions(+), 21 deletions(-)
Diffstat (limited to 'docs')
1 files changed, 8 insertions, 11 deletions
diff --git a/docs/overview.txt b/docs/overview.txt
index cd704aa..5e06afa 100644
--- a/docs/overview.txt
+++ b/docs/overview.txt
@@ -283,19 +283,16 @@ 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 >.config
+but is quite easy. The options to build a toolchain are saved with the
+toolchain, and you can retrieve this configuration by running:
+ ${CT_TARGET}-config
-will extract those options, prompt you for the new ones, which you can later
-edit with menuconfig.
+This will dump the configuration to stdout, so to rebuild a toolchain with this
+configuration, the following is all you need to do:
+ ${CT_TARGET}-config >.config
-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 >.config
-Then, once the configuration has been extracted, run:
- ct-ng oldconfig
+Then, you can review and change the configuration by running:
+ ct-ng menuconfig