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(-)
1 diff -durN duma_2_5_14.orig/Makefile duma_2_5_14/Makefile
2 --- duma_2_5_14.orig/Makefile 2008-03-13 00:54:10.000000000 +0100
3 +++ duma_2_5_14/Makefile 2008-06-17 10:28:45.000000000 +0200
17 createconf$(EXEPOSTFIX): createconf.o
18 - $(RMFORCE) createconf$(EXEPOSTFIX)
19 - $(CC) $(CFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)
20 + $(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)
22 tstheap$(EXEPOSTFIX): libduma.a tstheap.o
23 - $(RMFORCE) tstheap$(EXEPOSTFIX)
25 # define rules how to build objects for createconf
28 - $(CC) $(CFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@
29 + $(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@