scripts/build/debug/000-template.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Jan 01 17:49:44 2012 +0100 (2012-01-01)
changeset 2924 0eab838768b1
parent 1901 bdb3a98e064b
permissions -rw-r--r--
cc/gcc: install the core compilers in the build-tools dir

There really is no good reason to install the core compilers in their
own places, one for each pass. We can install them with the other
build tools.

Also, this implies that:
- there are fewer directories to save/restore
- there are fewer symlinks to create for binutils
- the PATH is shorter

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.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