scripts/build/debug.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Jan 28 22:06:49 2011 +0100 (2011-01-28)
changeset 2284 7ede374110e5
parent 483 99724e410693
permissions -rw-r--r--
config: add an option not to remove the destination directory

In certain circumstances, removing the destination/installation directory
is a bad idea. For example, when the build environment is already taking
care of sanitising the build tree, and pre-installs stuff in there, it is
a very bad idea to remove the destination directory.

This happens now in buildroot, as the crostool-NG backend now installs the
toolchain in the common host-tools directory, and pre-install there a few
host-utilities (eg. host-automake and host-gawk).

Provide a config knob to turn on/off the removal of the destination
directory, defaulting to 'y' (previous behavior), and forced to 'n' when
used as a backend.

Reported-by: Peter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     1 # Wrapper to build the debug facilities
     2 
     3 # List all debug facilities, and parse their scripts
     4 CT_DEBUG_FACILITY_LIST=
     5 for f in "${CT_LIB_DIR}/scripts/build/debug/"*.sh; do
     6     _f="$(basename "${f}" .sh)"
     7     _f="${_f#???-}"
     8     __f="CT_DEBUG_${_f}"
     9     if [ "${!__f}" = "y" ]; then
    10         CT_DoLog DEBUG "Enabling debug '${_f}'"
    11         . "${f}"
    12         CT_DEBUG_FACILITY_LIST="${CT_DEBUG_FACILITY_LIST} ${_f}"
    13     else
    14         CT_DoLog DEBUG "Disabling debug '${_f}'"
    15     fi
    16 done
    17 
    18 # Download the debug facilities
    19 do_debug_get() {
    20     for f in ${CT_DEBUG_FACILITY_LIST}; do
    21         do_debug_${f}_get
    22     done
    23 }
    24 
    25 # Extract and patch the debug facilities
    26 do_debug_extract() {
    27     for f in ${CT_DEBUG_FACILITY_LIST}; do
    28         do_debug_${f}_extract
    29     done
    30 }
    31 
    32 # Build the debug facilities
    33 do_debug() {
    34     for f in ${CT_DEBUG_FACILITY_LIST}; do
    35         do_debug_${f}_build
    36     done
    37 }
    38