scripts/wrapper.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Dec 23 20:43:32 2010 +0100 (2010-12-23)
changeset 2307 2efd46963086
parent 1434 7e7290acccc1
permissions -rw-r--r--
buildtools: move to working directory

There is absolutely *no* reason for the buildtools (wrappers to gcc, g++,
as, ld... for the local machine) to be in the toolchain directory. Moreover,
they are removed after the build completes.

Move them out of the toolchain directory, and into the build directory (but
yet the part specific to the current toolchain). This means we no longer
need to explicitly remove them either, BTW, but we need to save/restore them
for the restart feature.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
yann@1402
     1
#!/bin/sh
yann@1401
     2
titus@1960
     3
# this wrapper will not work under BSD systems or others
titus@1960
     4
# not containig the GNU readlink.
titus@1960
     5
# Under those, wrapper.c will forcibly be used
titus@1960
     6
# regardless of the config file setting.
titus@1960
     7
bartvdrmeulen@1434
     8
canonicalizedname=$(readlink -nm "${0}")
bartvdrmeulen@1434
     9
dirname="$(dirname "${canonicalizedname}")"
bartvdrmeulen@1434
    10
basename="$(basename "${canonicalizedname}")"
yann@1401
    11
yann@1401
    12
ld_lib_path="$(dirname "${dirname}")/lib"
yann@1401
    13
yann@1401
    14
case ":${LD_LIBRARY_PATH}:" in
yann@1401
    15
    *":${ld_lib_path}:"*)   ;;
yann@1401
    16
    *)  LD_LIBRARY_PATH="${ld_lib_path}${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}";;
yann@1401
    17
esac
yann@1401
    18
yann@1401
    19
export LD_LIBRARY_PATH
yann@1402
    20
exec "${dirname}/.${basename}" "$@"