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(-)

 # Bare metal config options

 # EXPERIMENTAL

 config KERNEL_bare_metal

     select BARE_METAL

     help

       'Bare metal' refers to those programs that run without any kernel.

       You probably want to say 'y' here if you plan to use your compiler

       to build bootloaders. It is not yet suitable to build Linux kernels,

       though, because the APCI stuff relies on the target C library headers

       being available?!?!...