scripts/showTuple.sh.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Apr 15 00:22:42 2011 +0200 (2011-04-15)
changeset 2544 751c3f735ada
parent 1336 bc8b9381f637
child 2838 822af73497bf
permissions -rw-r--r--
scripts/internals: do not remove lib{32,64}/ symlinks after build

During the build, we create lib{32,64}/ symlinks out of the sysroot.
In some cases (eg. mingw32 target), these symlinks are still required
when running the toolchain. For other combinations, the symlinks are
without incidence, so they can be safely kept after the build.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     1 #!@@CT_bash@@
     2 
     3 # What we need:
     4 #  - the .config file
     5 
     6 # Parse the tools' paths configuration
     7 . "${CT_LIB_DIR}/paths.mk"
     8 
     9 # We'll need the stdout later, save it
    10 exec 7>&1
    11 
    12 # Parse the common functions
    13 . "${CT_LIB_DIR}/scripts/functions"
    14 
    15 # Don't care about any log file
    16 exec >/dev/null
    17 rm -f "${tmp_log_file}"
    18 
    19 # Parse the configuration file
    20 . .config.2
    21 
    22 # Parse architecture and kernel specific functions
    23 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
    24 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
    25 
    26 # Build CT_TARGET
    27 CT_DoBuildTargetTuple
    28 
    29 # All this for this single echo... :-( Sigh, I'll have to re-arrange things...
    30 echo "${CT_TARGET}" >&7