scripts/build/companion_tools/400-libtool.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu May 26 22:51:03 2011 +0200 (2011-05-26)
changeset 2481 30644208c955
parent 2309 2e0f0757289d
permissions -rw-r--r--
configure: add possibility to set arbitrary variable in check_for

If check_for is able to find the required prog/inc/lib, allow it to
set an arbitrary variable to 'y'. This variable is then pushed down
to the kconfig definition.

For example:
has_or_abort prog=foobar kconfig=has_foobar

If foobar is available, it yields a kconfig variable defaulting to y:
config CONFIGURE_has_foobar
bool
default y

If foobar is missing, it yields a kconfig variable defaulting to n:
config CONFIGURE_has_foobar
bool

Thus it is possible to depends on that variabel to show/hide options:
config SOME_FEATURE
bool
prompt "Some feature"
depends on CONFIGURE_has_foobar

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     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_DoExecLog ALL chmod -R u+w "${CT_SRC_DIR}/libtool-${CT_LIBTOOL_VERSION}"
    13     CT_Patch "libtool" "${CT_LIBTOOL_VERSION}"
    14 }
    15 
    16 do_companion_tools_libtool_build() {
    17     CT_DoStep EXTRA "Installing libtool"
    18     mkdir -p "${CT_BUILD_DIR}/build-libtool"
    19     CT_Pushd "${CT_BUILD_DIR}/build-libtool"
    20     
    21     CT_DoExecLog CFG \
    22     "${CT_SRC_DIR}/libtool-${CT_LIBTOOL_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 }