[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: question about libtool wrapper and plugins
From: |
Felix Salfelder |
Subject: |
Re: question about libtool wrapper and plugins |
Date: |
Thu, 16 Jan 2014 17:16:26 +0100 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
Hi Thomas.
thanks for your reply.
On Thu, Jan 16, 2014 at 03:56:04PM +0100, Thomas Jahns wrote:
> ./libtool --mode=execute main/program
digging deeper, it looks like libtool cannot resolve this. it would have
to guess the location from where files in ${pkglibdir} have come. or
take some extra hints...
for tests, the situation is resolved by the AM_TESTS_ENVIRONMENT
variable. perhaps i should look out for an analogue approach for
non-test-suite program execution. i'd really like not to implement my
own wrappers for this purpose. is there a way out already? an
enlightening example maybe?
I wrote
> FWIW, program_LDADD+= ../plugins/plugin.la has no effect at all. maybe
> it should (if there is no other way to do this)?
this is wrong -- i just didnt notice. when i reverted the noist_, the
comforting portability warning returned.
regards
felix
PS: still CC, please.