Hi Paul,
Paul "LeoNerd" Evans wrote:
[SNIP]
Alternatively, am I looking at this from the wrong direction? Maybe the
problem is that the exporting library isn't providing -Wl,-rpath in
its .pc file, to assist anyone else who wasn't using libtool to link it
(such as is the case here).
No , I
On Thu, 14 Feb 2019 23:21:26 +
"Paul \"LeoNerd\" Evans" wrote:
> My earlier suggested approach of trying to hunt down the .la files and
> generate/append extra -Wl,-rpath arguments appears to be working
> reliably though, so it may be that's the best approach. It does feel
> rather fragile
On Thu, 7 Feb 2019 15:20:32 +0100
Thomas Jahns wrote:
> Have you tried setting something like
>
> CC='libtool cc'
> CFLAGS='--mode=compile -some -other -flags -youd -use'
> LDFLAGS='--mode=link -some -further -link -flags'
I've been looking at that, and it doesn't seem to be an easy one.
Hello Paul,
On 2/6/19 2:21 PM, Paul "LeoNerd" Evans wrote:
Nowthen - my actual question concerns what happens when I am not using
libtool to build my program. Such a case is common when building
C-level integration libraries for dynamic languages (Perl in my case).
I can't get libtool to
Hi all,
A *slightly* offtopic question here but I'm hoping someone will be able
to offer some assistance.
First off, the all-libtool case for comparison. If I install some
libtool-based library, it drops some files in (for example)
$HOME/lib - these files primarily are the libfoo.so* collection
