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

# GMP and MPFR libraries config options

menu "GMP and MPFR"

config GMP_MPFR

    bool

    prompt "GMP and MPFR"

    help

      Recent gcc needs both GMP and MPFR to build some frontends.

      Say 'Y' here if you want to build those two libraries specifically

      for crosstool-NG.

      The packages that can use GMP and MPFR are:

        - binutils

        - gcc

        - gdb

config GMP_MPFR_TARGET

    bool

    prompt "Build libraries for the target"

    depends on GMP_MPFR

    depends on ! BARE_METAL

    default n

    help

      Also build libraries for the target. This can be usefull if you want

      to later build a compiler that will run on the target, or if you want

      to run gdb natively on the target.

if GMP_MPFR

source config/gmp_mpfr/gmp.in

source config/gmp_mpfr/mpfr.in

endif

endmenu