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

 # Overall toolchain configuration: paths, jobs, etc...

 menu "Paths and misc options"

 source "config/global/ct-behave.in"

 source "config/global/paths.in"

 source "config/global/download.in"

 source "config/global/extract.in"

 source "config/global/build-behave.in"

 source "config/global/logging.in"

 endmenu