Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
scripts/build/companion_tools/100-m4.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Mar 20 00:02:21 2011 +0100 (2011-03-20)
changeset 2339 730e2d63296b
parent 2154 250cdcc86441
permissions -rw-r--r--
scripts: leave changelog in build dir, copy to install dir

Users tend to look for the build log in the current working directory,
rather than in the toolchain's installation dir. While bundling the build
log in the toolchain installation dir is nice for distribution and review,
it can be easier to have the build log readily available in the working
directory, as it is quicker to get to it.

So, the build log stays in the working directory until the toolchain is
completely and successfully built, and then a (compressed) copy is made.

Reported-by: Trevor Woerner <twoerner@gmail.com>
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_BUILDTOOLS_PREFIX_DIR}"

    23     CT_DoExecLog ALL make

    24     CT_DoExecLog ALL make install

    25     CT_Popd

    26     CT_EndStep

    27 }
crosstool-ng