crosstool-ng: scripts/wrapper.in@2efd46963086

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>

     1 #!/bin/sh

     3 # this wrapper will not work under BSD systems or others

     4 # not containig the GNU readlink.

     5 # Under those, wrapper.c will forcibly be used

     6 # regardless of the config file setting.

     8 canonicalizedname=$(readlink -nm "${0}")

     9 dirname="$(dirname "${canonicalizedname}")"

    10 basename="$(basename "${canonicalizedname}")"

    12 ld_lib_path="$(dirname "${dirname}")/lib"

    14 case ":${LD_LIBRARY_PATH}:" in

    15     *":${ld_lib_path}:"*)   ;;

    16     *)  LD_LIBRARY_PATH="${ld_lib_path}${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}";;

    17 esac

    19 export LD_LIBRARY_PATH

    20 exec "${dirname}/.${basename}" "$@"

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--