Get rid of CT_LIBC_FILE, remove useless CT_MakeAbsolutePath.
CT_LIBC_FILE:
- that one was not easy, as it had sneaked into CT_ExtractAndPatch
- which in turn made CT_ExtractAndPatch have references to C library addons
- which in turn relieved the C library _extract functions from doing their own job
- which in turn imposed some nasty tricks in CT_ExtractAndPatch
- which in turn made life easier for the DUMA _get and _extract functions
- which unveiled some bizare behavior for pushd and popd:
- if using smthg ike: 'pushd foo |bar':
- the directory is *neither* changed
- *nor* is it pushed onto the stack
- which made popd fail
CT_MakeAbsolutePath:
- used only to make CT_LOCAL_TARBALLS_DIR canonical
- which is ((almost) useless:
- hopefully, the user entered a full path already
- if it's not the case, too bad...
/trunk/scripts/build/debug/200-duma.sh | 5 1 4 0 +--
/trunk/scripts/build/libc/glibc.sh | 61 32 29 0 +++++++++++++++++---------------
/trunk/scripts/build/libc/uClibc.sh | 16 10 6 0 +++++---
/trunk/scripts/build/libc/eglibc.sh | 48 26 22 0 ++++++++++++++-----------
/trunk/scripts/crosstool.sh | 8 0 8 0 ----
/trunk/scripts/functions | 77 15 62 0 ++++++++--------------------------------
6 files changed, 84 insertions(+), 131 deletions(-)
1 # Template file for a debug utility
3 # Put your download code here
4 do_debug_foobar_get() {
6 # CT_GetFile "foobar-${CT_FOOBAR_VERSION}" http://foobar.com/releases/
10 # Put your extract code here
11 do_debug_foobar_extract() {
13 # CT_ExtractAndPatch "foobar-${CT_FOOBAR_VERSION}"
17 # Put your build code here
18 do_debug_foobar_build() {
20 # mkdir -p "${CT_BUILD_DIR}/build-foobar"
21 # CT_Pushd "${CT_BUILD_DIR}/build-foobar"
23 # "${CT_SRC_DIR}/foobar-${CT_FOOBAR_VERSION}/configure" \
24 # --build=${CT_BUILD} \
25 # --host=${CT_TARGET} \
28 # CT_DoExecLog ALL make
29 # CT_DoExecLog ALL make DESTDIR="${CT_SYSROOT_DIR}" install