-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Friesenhahn wrote:
| On Thu, 4 Mar 2004, Gary V. Vaughan wrote:
|
|I have a feeling that this is all done automatically by lt_dlopen. If it
|isn't then it should be...
|
|Comments?
|
|
| It seems to me that this text covers the case when libltdl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter O'Gorman wrote:
| Last time I looked lt_dlopen did all of this.
Indeedy :-)
| It seems that we ought to recommend that libname.la be the filename
| passed to lt_dlopen(), things probably work best in that case, but hey,
| you're the one with
On Thu, 4 Mar 2004, Gary V. Vaughan wrote:
I have a feeling that this is all done automatically by lt_dlopen. If it
isn't then it should be...
Comments?
It seems to me that this text covers the case when libltdl is not
used. It is possible to use modules built by libtool without using
Gary V. Vaughan wrote:
The current libtool docs say:
@node Finding the dlname
@section Finding the correct name to dlopen
@cindex names of dynamic modules
@cindex dynamic modules, names
After a library has been linked with @samp{-module}, it can be dlopened.
Unfortunately, because of the
On Thu, Mar 04, 2004 at 06:29:16PM +, 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/libhello.la}, and the @var{dlname} was
@file{libhello.so.3},
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The current libtool docs say:
@node Finding the dlname
@section Finding the correct name to dlopen
@cindex names of dynamic modules
@cindex dynamic modules, names
After a library has been linked with @samp{-module}, it can be dlopened.
Unfortunately,
