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