scripts/build/companion_tools/100-m4.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 1901 bdb3a98e064b
child 2309 2e0f0757289d
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 # Build script for m4
     2 
     3 CT_M4_VERSION=1.4.13
     4 
     5 do_companion_tools_m4_get() {
     6     CT_GetFile "m4-${CT_M4_VERSION}" \
     7                {ftp,http}://ftp.gnu.org/gnu/m4
     8 }
     9 
    10 do_companion_tools_m4_extract() {
    11     CT_Extract "m4-${CT_M4_VERSION}"
    12     CT_Patch "m4" "${CT_M4_VERSION}"
    13 }
    14 
    15 do_companion_tools_m4_build() {
    16     CT_DoStep EXTRA "Installing m4"
    17     mkdir -p "${CT_BUILD_DIR}/build-m4"
    18     CT_Pushd "${CT_BUILD_DIR}/build-m4"
    19     
    20     CT_DoExecLog CFG \
    21     "${CT_SRC_DIR}/m4-${CT_M4_VERSION}/configure" \
    22         --prefix="${CT_TOOLS_OVERIDE_DIR}"
    23     CT_DoExecLog ALL make
    24     CT_DoExecLog ALL make install
    25     CT_Popd
    26     CT_EndStep
    27 }