scripts/build/debug/000-template.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 1901 bdb3a98e064b
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>
     1 # Template file for a debug utility
     2 
     3 # Put your download code here
     4 do_debug_foobar_get() {
     5     # For example:
     6     # CT_GetFile "foobar-${CT_FOOBAR_VERSION}" http://foobar.com/releases/
     7     :
     8 }
     9 
    10 # Put your extract code here
    11 do_debug_foobar_extract() {
    12     # For example:
    13     # CT_Extract "foobar-${CT_FOOBAR_VERSION}"
    14     # CT_Patch "foobar" "${CT_FOOBAR_VERSION}"
    15     :
    16 }
    17 
    18 # Put your build code here
    19 do_debug_foobar_build() {
    20     # For example:
    21     # mkdir -p "${CT_BUILD_DIR}/build-foobar"
    22     # CT_Pushd "${CT_BUILD_DIR}/build-foobar"
    23     # CT_DoExecLog CFG                                        \
    24     # "${CT_SRC_DIR}/foobar-${CT_FOOBAR_VERSION}/configure"   \
    25     #     --build=${CT_BUILD}                                 \
    26     #     --host=${CT_TARGET}                                 \
    27     #     --prefix=/usr                                       \
    28     #     --foobar-options
    29     # CT_DoExecLog ALL make
    30     # CT_DoExecLog ALL make DESTDIR="${CT_SYSROOT_DIR}" install
    31     # CT_Popd
    32     :
    33 }
    34