crosstool-ng/scripts/build/debug/000-template.sh
Yann E. MORIN" ff1d30c4a3 For tools/ and debug/ build scripts, annd a numeric prefix, so that they always get built in the same order, in case of library dependencies.
/trunk/scripts/build/debug.sh |    2     1     1     0 +-
 /trunk/scripts/build/tools.sh |    2     1     1     0 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
2008-05-02 21:59:14 +00:00

51 lines
1.5 KiB
Bash

# Template file for a debug utility
# Check here wether your debug tool is enabled or not.
# This will get redefined over and over again for each tool, so don't
# count on it in the functions below.
is_enabled="${CT_FOOBAR}"
# Small function to print the filename
# Note that this function gets redefined over and over for each tool
# It's of no use when building the toolchain proper, but shows all its
# usefullness when saving the toolchain and building the tarball.
# You shall not echo anything if you're not enabled!
# Echo the name of the file, without the extension, below.
do_print_filename() {
# For example:
# [ "${CT_FOOBAR}" = "y" ] || return 0
# echo "foobar-${CT_FOOBAR_VERSION}"
:
}
# Put your download code here
do_debug_foobar_get() {
# For example:
# CT_GetFile "foobar-${CT_FOOBAR_VERSION}" http://foobar.com/releases/
:
}
# Put your extract code here
do_debug_foobar_extract() {
# For example:
# CT_ExtractAndPatch "foobar-${CT_FOOBAR_VERSION}"
:
}
# Put your build code here
do_debug_foobar_build() {
# For example:
# mkdir -p "${CT_BUILD_DIR}/build-foobar"
# CT_Pushd "${CT_BUILD_DIR}/build-foobar"
# "${CT_SRC_DIR}/foobar-${CT_FOOBAR_VERSION}/configure" \
# --build=${CT_BUILD} \
# --host=${CT_TARGET} \
# --prefix=/usr \
# --foobar-options
# make
# make DESTDIR="${CT_SYSROOT_DIR}" install
# CT_Popd
:
}