scripts/build/companion_tools/400-libtool.sh
author Bart vdr. Meulen <bartvdrmeulen@gmail.com>
Mon Jul 19 23:16:02 2010 +0200 (2010-07-19)
changeset 2031 3917f2dafed1
parent 1730 c43d16b6b950
child 2154 250cdcc86441
permissions -rw-r--r--
complibs: fix using static companion libraries

When building a cross-compiler for a target which uses a file extension for
binaries the symbolic link to cc is not created correctly because the lookup
of the gcc binary is done in a incorrect path

Signed-off-by: Bart vdr. Meulen <bartvdrmeulen@gmail.com>
     1 # Build script for libtool
     2 
     3 CT_LIBTOOL_VERSION=2.2.6b
     4 
     5 do_companion_tools_libtool_get() {
     6     CT_GetFile "libtool-${CT_LIBTOOL_VERSION}" \
     7                {ftp,http}://ftp.gnu.org/gnu/libtool
     8 }
     9 
    10 do_companion_tools_libtool_extract() {
    11     CT_Extract "libtool-${CT_LIBTOOL_VERSION}"
    12     CT_Patch "libtool" "${CT_LIBTOOL_VERSION}"
    13 }
    14 
    15 do_companion_tools_libtool_build() {
    16     CT_DoStep EXTRA "Installing libtool"
    17     mkdir -p "${CT_BUILD_DIR}/build-libtool"
    18     CT_Pushd "${CT_BUILD_DIR}/build-libtool"
    19     
    20     CT_DoExecLog ALL \
    21     "${CT_SRC_DIR}/libtool-${CT_LIBTOOL_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 }