Extract the config files related stuff from the kconfig stuff
- create config/config.mk, with all the config.gen/ rules
- the only common points between config files and configurators:
- the top-level config file to include, stored in KCONFIG_TOP
- the config_file rules, which makes config files available to configurators
- dependency-files are renamed from %.d to %.dep (.d is reserved for directories)
- a few eye-candy here and there

/trunk/kconfig/kconfig.mk | 184 12 172 0 +++--------------------------------------------------
/trunk/config/config.mk | 118 9 109 0 +++-------------------------------
/trunk/ct-ng.in | 1 1 0 0 +
3 files changed, 22 insertions(+), 281 deletions(-)

 # ARM specific configuration file

 config ARCH_arm

     select ARCH_SUPPORTS_BOTH_ENDIAN

     select ARCH_DEFAULT_LE

     select ARCH_SUPPORT_ARCH

     select ARCH_SUPPORT_CPU

     select ARCH_SUPPORT_TUNE

     select ARCH_SUPPORT_FPU

     help

       The ARM architecture, as defined by:

         http://www.arm.com/

 config ARCH_ARM_EABI

     bool

     prompt "Use EABI"

     default n

     help

       Set up the toolchain so that it generates EABI-compliant binaries.

 config ARCH_ARM_ABI_OK

     bool

     default y

     depends on ! ARCH_ARM_EABI

     select ARCH_SUPPORT_ABI