scripts/build/companion_tools/100-m4.sh
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Dec 27 12:45:22 2012 +0100 (2012-12-27)
changeset 3152 b286c7993be5
parent 2154 250cdcc86441
permissions -rw-r--r--
scripts/addToolsVersion: properly handle .in vs. .in.2

While most components have their version in the .in file, some
have it in the .in.2 (eg. elf2flt).

Currently, to handle this case, we indiscriminately munge both files,
but this is wrong: in the elf2flt case, if we add a binutils version,
we do not want it to be added to elf2flt, and conversely.

So, for each tool, we need to explicitly know what file to munge.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
richard@1728
     1
# Build script for m4
richard@1728
     2
richard@1728
     3
CT_M4_VERSION=1.4.13
richard@1728
     4
richard@1728
     5
do_companion_tools_m4_get() {
richard@1728
     6
    CT_GetFile "m4-${CT_M4_VERSION}" \
richard@1728
     7
               {ftp,http}://ftp.gnu.org/gnu/m4
richard@1728
     8
}
richard@1728
     9
richard@1728
    10
do_companion_tools_m4_extract() {
richard@1728
    11
    CT_Extract "m4-${CT_M4_VERSION}"
yann@1901
    12
    CT_Patch "m4" "${CT_M4_VERSION}"
richard@1728
    13
}
richard@1728
    14
richard@1728
    15
do_companion_tools_m4_build() {
richard@1728
    16
    CT_DoStep EXTRA "Installing m4"
richard@1728
    17
    mkdir -p "${CT_BUILD_DIR}/build-m4"
richard@1728
    18
    CT_Pushd "${CT_BUILD_DIR}/build-m4"
richard@1728
    19
    
anthony@2154
    20
    CT_DoExecLog CFG \
richard@1728
    21
    "${CT_SRC_DIR}/m4-${CT_M4_VERSION}/configure" \
yann@2309
    22
        --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"
richard@1728
    23
    CT_DoExecLog ALL make
richard@1728
    24
    CT_DoExecLog ALL make install
richard@1728
    25
    CT_Popd
richard@1728
    26
    CT_EndStep
richard@1728
    27
}