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 # Template file for a debug utility
3 # Check here wether your debug tool is enabled or not.
4 # This will get redefined over and over again for each tool, so don't
5 # count on it in the functions below.
6 is_enabled="${CT_FOOBAR}"
8 # Small function to print the filename
9 # Note that this function gets redefined over and over for each tool
10 # It's of no use when building the toolchain proper, but shows all its
11 # usefullness when saving the toolchain and building the tarball.
12 # You shall not echo anything if you're not enabled!
13 # Echo the name of the file, without the extension, below.
16 # [ "${CT_FOOBAR}" = "y" ] || return 0
17 # echo "foobar-${CT_FOOBAR_VERSION}"
21 # Put your download code here
22 do_debug_foobar_get() {
24 # CT_GetFile "foobar-${CT_FOOBAR_VERSION}" http://foobar.com/releases/
28 # Put your extract code here
29 do_debug_foobar_extract() {
31 # CT_ExtractAndPatch "foobar-${CT_FOOBAR_VERSION}"
35 # Put your build code here
36 do_debug_foobar_build() {
38 # mkdir -p "${CT_BUILD_DIR}/build-foobar"
39 # CT_Pushd "${CT_BUILD_DIR}/build-foobar"
41 # "${CT_SRC_DIR}/foobar-${CT_FOOBAR_VERSION}/configure" \
42 # --build=${CT_BUILD} \
43 # --host=${CT_TARGET} \
46 # CT_DoExecLog ALL make
47 # CT_DoExecLog ALL make DESTDIR="${CT_SYSROOT_DIR}" install