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 # Wrapper to build the tools facilities
3 # List all tools facilities, and parse their scripts
4 CT_TOOLS_FACILITY_LIST=
5 for f in "${CT_LIB_DIR}/scripts/build/tools/"*.sh; do
8 f=$(basename "${f}" .sh)
9 if [ "${is_enabled}" = "y" ]; then
10 CT_TOOLS_FACILITY_LIST="${CT_TOOLS_FACILITY_LIST} ${f#???-}"
14 # Download the tools facilities
16 for f in ${CT_TOOLS_FACILITY_LIST}; do
21 # Extract and patch the tools facilities
23 for f in ${CT_TOOLS_FACILITY_LIST}; do
28 # Build the tools facilities
30 for f in ${CT_TOOLS_FACILITY_LIST}; do