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/kconfig.mk | 9 2 7 0 ++-------
/trunk/scripts/crosstool.sh | 6 5 1 0 +++++-
/trunk/docs/overview.txt | 21 9 12 0 +++++++++------------
/trunk/tools/toolchain-config.in | 8 8 0 0 ++++++++
/trunk/ct-ng.comp | 2 1 1 0 +-
5 files changed, 25 insertions(+), 21 deletions(-)
1 # Makefile for each steps
2 # Copyright 2006 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
4 CT_STEPS := libc_check_config \
25 @$(CT_NG) RESTART=$@ STOP=$@ build
27 $(patsubst %,+%,$(CT_STEPS)):
28 @$(CT_NG) STOP=$(patsubst +%,%,$@) build
30 $(patsubst %,%+,$(CT_STEPS)):
31 @$(CT_NG) RESTART=$(patsubst %+,%,$@) build
34 @echo ' list-steps - List all build steps'
37 @echo 'Available build steps, in order:'
38 @for step in $(CT_STEPS); do \
41 @echo 'Use "$(CT_NG) <step>" to execute only that step.'
42 @echo 'Use "$(CT_NG) +<step>" to execute up to that step.'
43 @echo 'Use "$(CT_NG) <step>+" to execute from that step onward.'