crosstool-ng/scripts/toolchain-config.in

#!/bin/sh

tail -n+5 "${0}" |bzcat
exit 0
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(-) 2008-10-01 18:10:40 +00:00			`#!/bin/sh`

scripts: simplify and fix the toolchain config script The script that is installed, and which sole purpose is to dump the .config that was used to build the toolchain, is pure insanity. Let's make it much, much more simpler... Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 2011-08-18 22:52:05 +00:00			`tail -n+5 "${0}" \|bzcat`
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(-) 2008-10-01 18:10:40 +00:00			`exit 0`