Testing a dlopened library

[Roger Ferrer Ibáñez]

Hi,

I'm writing an application that generates both an executable and a 
library that acts like a plugin, so sometimes is dlopened at runtime.


The problem arises when checking the application by means of 'make 
check'. If the application has not been installed yet, the dlopened 
library is not found (because it still resides somewhere in a given .lib 
subdirectory of one builddir) and the test fails.


If the application has been installed, the installed library is dlopened 
instead, so it is not actually checking the library just built but the 
one previously installed.


This problem renders things like 'make distcheck' almost useless because 
this test fails, since 'make install' is performed later than 'make 
check' in automake's distcheck.


I assume that this is the expected behaviour: dlopened shared objects 
are not properly found until installed, isn't it? So, I wonder, how is 
this issue workarounded? Are testsuites modified so LD_LIBRARY_PATH is 
updated to include the proper .lib directory?


Thanks a lot,

--
Roger Ferrer Ibáñez - [EMAIL PROTECTED]


___
http://lists.gnu.org/mailman/listinfo/libtool

libtool 2.2 release pending?

[Bob Friesenhahn]

Is the libtool release scheduled for this weekend, or for next 
weekend?


Thanks,

Bob
==
Bob Friesenhahn
[EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/



___
http://lists.gnu.org/mailman/listinfo/libtool

Re: libtool 2.2 release pending?

[Ralf Wildenhues]

* Bob Friesenhahn wrote on Thu, Feb 21, 2008 at 08:47:04PM CET:
 Is the libtool release scheduled for this weekend, or for next 
 weekend?

Depends on whether I find time this, or Gary next weekend.

Cheers,
Ralf


___
http://lists.gnu.org/mailman/listinfo/libtool