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

 # Super-H specific configuration file

 # EXPERIMENTAL

 config ARCH_sh

     select ARCH_SUPPORTS_BOTH_ENDIAN

     select ARCH_DEFAULT_LE

     help

       The Super-H architecture, as defined by:

         http://www.renesas.com/fmwk.jsp?cnt=superh_family_landing.jsp&fp=/products/mpumcu/superh_family/

 choice

     bool

     prompt "Variant"

 config ARCH_SH_SH3

     bool

     prompt "sh3"

 config ARCH_SH_SH4

     bool

     prompt "sh4"

 config ARCH_SH_SH4A

     bool

     prompt "sh4a"

 endchoice

 config ARCH_SH_VARIANT

     string

     default "sh3"   if ARCH_SH_SH3

     default "sh4"   if ARCH_SH_SH4

     default "sh4a"  if ARCH_SH_SH4A