Cheesy kconfig stuff:
- silent/quiet/verbose build:
- ct-ng by default only prints quit messages, such as "CC xxx",
- if using V=0, nothing is printed,
- if using V=1, the full command lines are printed,
- other values are indeterminate,
- should help in debugging the kconfig stuff;
- complete kconfig/{,m}conf generation:
- fully dynamic dependencies on source files,
- compilation of .c into .o, then linking (instead of direct linking),
- VPATH usage when not --local;
Typo + a coment moved.

/trunk/kconfig/kconfig.mk | 140 87 53 0 +++++++++++++++++++++++++++++++++--------------------
/trunk/tools/tools.mk | 12 6 6 0 ++--
/trunk/steps.mk | 6 3 3 0 +-
/trunk/samples/samples.mk | 30 15 15 0 +++++-----
/trunk/ct-ng.in | 40 28 12 0 +++++++++++----
5 files changed, 139 insertions(+), 89 deletions(-)

 # Compute ARM-specific values

 CT_DoArchValues() {

     # The architecture part of the tuple:

     CT_TARGET_ARCH="${CT_ARCH}${target_endian_eb}"

     # The system part of the tuple:

     case "${CT_LIBC},${CT_ARCH_ARM_EABI}" in

         *glibc,y)   CT_TARGET_SYS=gnueabi;;

         uClibc,y)   CT_TARGET_SYS=uclibcgnueabi;;

         none,y)     CT_TARGET_SYS=eabi;;

     esac

     # In case we're EABI, do *not* specify any ABI!

     # which means, either we do not have an ABI specified, or we're not EABI.

     CT_TestOrAbort "Internal error: CT_ARCH_ABI should not be set for EABI build." -z "${CT_ARCH_ABI}" -o -z "${CT_ARCH_ARM_EABI}"

 }