On Wed, 18 Apr 2007, Bob Friesenhahn wrote:
Years ago, I converted ImageMagick to use loadable modules in order to
decouple from optional libraries. This did require a clean "codec" interface
but it turned out fine. There are 95 modules, and libldtl is only used if
the package is built to us
* Reuben Thomas wrote on Wed, Apr 18, 2007 at 03:31:38PM CEST:
> On Tue, 17 Apr 2007, Ralf Wildenhues wrote:
>
> >If you can find out the set of libraries at 'configure' time, then there
> >is no need for dlopen.
>
> There is in my case: I do know the set of libraries at configure time, but
> I
On Tue, 17 Apr 2007, Ralf Wildenhues wrote:
If you can find out the set of libraries at 'configure' time, then there
is no need for dlopen.
There is in my case: I do know the set of libraries at configure time, but I
can't link against all of them. The particular case I have in mind is
build
Hello Reuben,
To add to Bob's answer:
* Reuben Thomas wrote on Mon, Apr 16, 2007 at 02:01:24AM CEST:
>
> I want to be able to link against a library which may not be present at
> runtime, be certain that the application starts up (i.e. the dynamic linker
> doesn't discover that a library is mis
On Mon, 16 Apr 2007, Reuben Thomas wrote:
This is a function of libltdl, which comes with libtool. I use it in
GraphicsMagick.
I read the documentation for libltdl before posting originally, but I
couldn't see how to do what I wanted. Can you explain, please? In particular,
I couldn't see h
On Sun, 15 Apr 2007, Bob Friesenhahn wrote:
On Mon, 16 Apr 2007, Reuben Thomas wrote:
Is there a way to use libtool to link against a library using dlopen? I
want to be able to link against a library which may not be present at
runtime, be certain that the application starts up (i.e. the dyna
