Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
scripts/build/companion_tools/300-automake.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Jan 01 17:49:44 2012 +0100 (2012-01-01)
changeset 2924 0eab838768b1
parent 2309 2e0f0757289d
permissions -rw-r--r--
cc/gcc: install the core compilers in the build-tools dir

There really is no good reason to install the core compilers in their
own places, one for each pass. We can install them with the other
build tools.

Also, this implies that:
- there are fewer directories to save/restore
- there are fewer symlinks to create for binutils
- the PATH is shorter

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 
     1 # Build script for automake

     2 

     3 CT_AUTOMAKE_VERSION=1.11.1

     4 

     5 do_companion_tools_automake_get() {

     6     CT_GetFile "automake-${CT_AUTOMAKE_VERSION}" \

     7                {ftp,http}://ftp.gnu.org/gnu/automake

     8 }

     9 

    10 do_companion_tools_automake_extract() {

    11     CT_Extract "automake-${CT_AUTOMAKE_VERSION}"

    12     CT_DoExecLog ALL chmod -R u+w "${CT_SRC_DIR}/automake-${CT_AUTOMAKE_VERSION}"

    13     CT_Patch "automake" "${CT_AUTOMAKE_VERSION}"

    14 }

    15 

    16 do_companion_tools_automake_build() {

    17     CT_DoStep EXTRA "Installing automake"

    18     mkdir -p "${CT_BUILD_DIR}/build-automake"

    19     CT_Pushd "${CT_BUILD_DIR}/build-automake"

    20     

    21     CT_DoExecLog CFG \

    22     "${CT_SRC_DIR}/automake-${CT_AUTOMAKE_VERSION}/configure" \

    23         --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"

    24     CT_DoExecLog ALL make

    25     CT_DoExecLog ALL make install

    26     CT_Popd

    27     CT_EndStep

    28 }
crosstool-ng