[Top][All Lists]

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

Re: Dlopening documentation

From: Albert Chin
Subject: Re: Dlopening documentation
Date: Mon, 8 Mar 2004 18:43:44 -0600
User-agent: Mutt/1.4i

On Thu, Mar 04, 2004 at 06:29:16PM +0000, Gary V. Vaughan wrote:
> If @var{dlname} is empty, then the library cannot be dlopened.
> Otherwise, it gives the dlname of the library.  So, if the library was
> installed as @file{/usr/local/lib/}, and the @var{dlname} was
> @file{}, then @file{/usr/local/lib/} should be
> dlopened.
> If your program uses this approach, then it should search the
> directories listed in the @address@hidden@code{LIBPATH}
> on AIX, and @code{SHLIB_PATH} on HP-UX.} environment variable, as well as
> the directory where libraries will eventually be installed.  Searching
> this variable (or equivalent) will guarantee that your program can find
> its dlopened modules, even before installation, provided you have linked
> them using libtool.
> I have a feeling that this is all done automatically by lt_dlopen.  If it
> isn't then it should be...

Yes, it should be. BTW, how do we handle the case where

albert chin (address@hidden)

reply via email to

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