LD_LIBRARY_PATH exorcism
authorColin Walters <walters@verbum.org>
Thu, 20 Aug 2009 22:21:41 +0000 (18:21 -0400)
committerColin Walters <walters@verbum.org>
Mon, 24 Aug 2009 18:14:53 +0000 (14:14 -0400)
commitbacb23155a5fb370493d0ce2fc438ea6c2982a45
tree685b1598528c1fe9f8e54425205197d84dca1338
parent3d4a06e80a46964b2f1a3bfc33403e89022a4163
LD_LIBRARY_PATH exorcism

Thanks to commit 6d510b8db, we now no longer need LD_LIBRARY_PATH
to be set for invoking the compiler.

Next, before we were taking the LD_LIBRARY_PATH variable and
turning it into a compile path, presumably to attempt to handle
the cases where we weren't getting the right -L flags.  Also
interacting with this was a while ago we weren't really doing
uninstalled libtool libraries correctly, which is probably
how hacks involving LD_LIBRARY_PATH crept into the scanner.

Just require that we're passed the right -L flags, and we
should be doing libtool libraries better now.
gir/Makefile.am
giscanner/scannermain.py
tests/invoke/Makefile.am
tests/offsets/Makefile.am
tests/scanner/Makefile.am