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 # GMP and MPFR libraries config options
9 Recent gcc needs both GMP and MPFR to build some frontends.
11 Say 'Y' here if you want to build those two libraries specifically
14 The packages that can use GMP and MPFR are:
19 config GMP_MPFR_TARGET
21 prompt "Build libraries for the target"
23 depends on ! BARE_METAL
26 Also build libraries for the target. This can be usefull if you want
27 to later build a compiler that will run on the target, or if you want
28 to run gdb natively on the target.
31 source config/gmp_mpfr/gmp.in
32 source config/gmp_mpfr/mpfr.in