scripts/build/companion_tools/400-libtool.sh
author Anthony Foiani <anthony.foiani@gmail.com>
Fri Oct 22 22:02:57 2010 +0200 (2010-10-22)
changeset 2154 250cdcc86441
parent 1901 bdb3a98e064b
child 2309 2e0f0757289d
permissions -rw-r--r--
scripts: add "FILE" and "CFG" debug levels.

I ran into some minor difficulties looking through the build log for a
particular file: I wasn't interested in seeing it unpacked, but only
when it is built or installed. Adding these two levels allows me to
differentiate between those cases.

[Yann E. MORIN: Those are blind log levels, and are used only to search
in the build-log afterward.]

Signed-off-by: Anthony Foiani <anthony.foiani@gmail.com>
richard@1730
     1
# Build script for libtool
richard@1730
     2
richard@1730
     3
CT_LIBTOOL_VERSION=2.2.6b
richard@1730
     4
richard@1730
     5
do_companion_tools_libtool_get() {
richard@1730
     6
    CT_GetFile "libtool-${CT_LIBTOOL_VERSION}" \
richard@1730
     7
               {ftp,http}://ftp.gnu.org/gnu/libtool
richard@1730
     8
}
richard@1730
     9
richard@1730
    10
do_companion_tools_libtool_extract() {
richard@1730
    11
    CT_Extract "libtool-${CT_LIBTOOL_VERSION}"
yann@1901
    12
    CT_Patch "libtool" "${CT_LIBTOOL_VERSION}"
richard@1730
    13
}
richard@1730
    14
richard@1730
    15
do_companion_tools_libtool_build() {
richard@1730
    16
    CT_DoStep EXTRA "Installing libtool"
richard@1730
    17
    mkdir -p "${CT_BUILD_DIR}/build-libtool"
richard@1730
    18
    CT_Pushd "${CT_BUILD_DIR}/build-libtool"
richard@1730
    19
    
anthony@2154
    20
    CT_DoExecLog CFG \
richard@1730
    21
    "${CT_SRC_DIR}/libtool-${CT_LIBTOOL_VERSION}/configure" \
richard@1730
    22
        --prefix="${CT_TOOLS_OVERIDE_DIR}"
richard@1730
    23
    CT_DoExecLog ALL make
richard@1730
    24
    CT_DoExecLog ALL make install
richard@1730
    25
    CT_Popd
richard@1730
    26
    CT_EndStep
richard@1730
    27
}