crosstool-ng/scripts/build/debug/000-template.sh
Bryan Hundven 6f8e89cb5c consistency: Use exported variables of required tools
We check for apps:

* make
* sed
* grep
* awk
* libtool/libtoolize
* install
* patch
* and more

...during configure. Our scripts should be consistent about using the
variables that define where the found tool was found.

Of course, we do hard-link these tools in buildtools, but that should be
a backup for the components we are building. Our scripts should always
use the tools we find.

Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-17 02:48:09 -08:00

35 lines
1005 B
Bash

# Template file for a debug utility
# 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_Extract "foobar-${CT_FOOBAR_VERSION}"
# CT_Patch "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_DoExecLog CFG \
# "${CT_SRC_DIR}/foobar-${CT_FOOBAR_VERSION}/configure" \
# --build=${CT_BUILD} \
# --host=${CT_TARGET} \
# --prefix=/usr \
# --foobar-options
# CT_DoExecLog ALL ${make}
# CT_DoExecLog ALL ${make} DESTDIR="${CT_SYSROOT_DIR}" install
# CT_Popd
:
}