Re: Developing against $HOME/lib libraries and LD_LIBRARY_PATH
"Paul \"LeoNerd\" Evans" <[email protected]>
| Newsgroups | gmane.comp.gnu.libtool.general |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 30 Nov 2017 15:38:20 +0100 Thomas Jahns <[email protected]> wrote: > The -rpath argument is for libtool (to tell it where the library will > be installed). To tell libtool (or ld) where to search for libraries > at run-time (if no .la files are installed) one needs to add -R or > -Wl,-rpath options. So, should library A's .pc file include that in its output then? Is it safe to do that unconditionally, even if the library is really just installed in /usr/lib by the normal tooling? I wasn't sure if that was safe to do. -- Paul "LeoNerd" Evans [email protected] | https://metacpan.org/author/PEVANS http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/ _______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool
signature.asc
(application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQACtfoNPkrOD+dkiu8tLZMLxwGjQUCWiG3BAAKCRC8tLZMLxwG jTfIAKCOcJpklls5y3YuonWIM9Eil2MrGwCgzwuXrsx7d7kkXipacKrnF+7+vNI= =0lnJ -----END PGP SIGNATURE-----