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 # 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
6 _f="$(basename "${f}" .sh)"
9 if [ "${!__f}" = "y" ]; then
10 CT_DoLog DEBUG "Enabling tool '${_f}'"
12 CT_TOOLS_FACILITY_LIST="${CT_TOOLS_FACILITY_LIST} ${_f}"
14 CT_DoLog DEBUG "Disabling tool '${_f}'"
18 # Download the tools facilities
20 for f in ${CT_TOOLS_FACILITY_LIST}; do
25 # Extract and patch the tools facilities
27 for f in ${CT_TOOLS_FACILITY_LIST}; do
32 # Build the tools facilities
34 for f in ${CT_TOOLS_FACILITY_LIST}; do