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-06-17 10:30:40.000000000 +0200
3 +++ duma_2_5_14/Makefile 2008-06-17 10:30:17.000000000 +0200
5 dumatest.c tstheap.c thread-test.c testmt.c dumatestpp.cpp testoperators.cpp \
8 -OBJECTS = dumapp.o duma.o sem_inc.o print.o
9 +OBJECTS = duma.o sem_inc.o print.o
10 +SO_OBJECTS = duma_so.o sem_inc_so.o print_so.o
12 -SO_OBJECTS = dumapp_so.o duma_so.o sem_inc_so.o print_so.o
15 +SO_OBJECTS += dumapp_so.o
18 all: libduma.a tstheap$(EXEPOSTFIX) dumatest$(EXEPOSTFIX) thread-test$(EXEPOSTFIX) testmt$(EXEPOSTFIX) dumatestpp$(EXEPOSTFIX) testoperators$(EXEPOSTFIX) $(DUMA_DYN_DEPS)