[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Testing a dlopened library

From: Ralf Wildenhues
Subject: Re: Testing a dlopened library
Date: Fri, 22 Feb 2008 11:27:45 +0100
User-agent: Mutt/1.5.17 (2008-01-17)

Hello Roger,

* Roger Ferrer Ibáñez wrote on Thu, Feb 21, 2008 at 06:54:01PM CET:
> 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.

Try executing
  $LIBTOOL --mode=execute -dlopen foo/ -dlopen bar/ 

instead of

for your tests, with LIBTOOL set appropriately.

> 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?

Doing it manually is another possibility (but not all systems understand


reply via email to

[Prev in Thread] Current Thread [Next in Thread]