Re: Developing against $HOME/lib libraries and LD_LIBRARY_PATH

2017-12-01 Thread Paul "LeoNerd" Evans
On Fri, 1 Dec 2017 17:11:23 -0500 Nick Bowler wrote: > If library A is a libtool library then libtool should do the right > thing automatically. All you should need to do is add the libtool > library to your link command. > > If library A is not a libtool library then libtool won't necessarily

Re: Developing against $HOME/lib libraries and LD_LIBRARY_PATH

2017-12-01 Thread Nick Bowler
On 12/1/17, Paul "LeoNerd" Evans wrote: > On Thu, 30 Nov 2017 15:38:20 +0100 > Thomas Jahns 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

Re: Developing against $HOME/lib libraries and LD_LIBRARY_PATH

2017-12-01 Thread Paul "LeoNerd" Evans
On Thu, 30 Nov 2017 15:38:20 +0100 Thomas Jahns 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, sho

Re: Developing against $HOME/lib libraries and LD_LIBRARY_PATH

2017-11-30 Thread Thomas Jahns
Posting again, since at the first attempt I only sent directly to Paul. On 11/22/17 15:45, Paul "LeoNerd" Evans wrote: On Thu, 16 Nov 2017 14:49:01 -0500 Nick Bowler wrote: If that is not happening then maybe the libraries and/or programs are being linked incorrectly, or perhaps there's a bug

Re: Developing against $HOME/lib libraries and LD_LIBRARY_PATH

2017-11-22 Thread Paul "LeoNerd" Evans
On Thu, 16 Nov 2017 14:49:01 -0500 Nick Bowler wrote: > If that is not happening then maybe the libraries and/or programs are > being linked incorrectly, or perhaps there's a bug in libtool. > > Example: > > build+install libfoo to non-system location: > % libtool --tag=CC --mode=compile gcc

Re: Developing against $HOME/lib libraries and LD_LIBRARY_PATH

2017-11-16 Thread Nick Bowler
On 11/16/17, Paul "LeoNerd" Evans wrote: > I'm developing two different C libraries; lets just call them A and B. > A is fairly standalone, and B depends on A. [...] > But now suppose I have a possible change I want to make that needs > edits in both libraries. I don't want to build a new system p

Developing against $HOME/lib libraries and LD_LIBRARY_PATH

2017-11-16 Thread Paul "LeoNerd" Evans
Hi all, I've come up against an awkward situation using libtool, and I wonder if I could ask for some advice on what I'm probably doing wrong here. I'm developing two different C libraries; lets just call them A and B. A is fairly standalone, and B depends on A. Using libtool, I can develop on A