Comment 70 for bug 10832

Message-Id: <email address hidden>
Date: Fri, 3 Dec 2004 01:17:20 +0100
From: Achim Bohnet <email address hidden>
To: "Laurence J. Lane" <email address hidden>,
 <email address hidden>
Subject: Re: Bug#283339: more imlib2 vs digikam stuff

On Friday 03 December 2004 00:26, Laurence J. Lane wrote:

[Preface: no perfect explanation included below ;) ]
> I have another question. digikam has been using libimlib2
> for a long time now. Why does it suddenly have a problem
> with a lack of .la files for imlib2 plugins?

First digikam 0.7 is new. I never saw the problem because
I always had libimlib2-dev installed.

The new libImlib2 1.1.2 links again libltdl lib (or so, no access to
my sid system until monday) the libImlib2 1.1.0 in sarge does
not use libltdl lib.

I know that KDEs dyn loading for k-parts, services, etc since
some year relies on the existance of .la files. If this
influences the dynamic loading of libimlib. I don't kown :(

On Friday 03 December 2004 00:16, Laurence J. Lane wrote:
> I can't claim to know much of anything about dlopen or
> .la files, but tell me... what makes digikam have this
> requirement that no other packages linked to libimlib2 have?

Good question. Maybe others have libimlib2-dev also installed?

Here another 'vague' answer from Renchi the main digikam developer

----
some preface: imlib2 uses dynamically loaded file-loaders to load
different file formats (is that statement loaded enough :)). to determine
the location and type of loaders, imlib2 just needs to check the .so files
in its loader directories. but when used in conjuction with kde, the
dynamic loading of the .so files is somehow influenced (i'm not clear in
the details of this). i believe the .la files installed with the loaders
are being forced to be used (when used with kde), and if there is an
incompatibility between the location indicated by the .la files (for the
.so files) and the actual .so file location, the .so files will fail to
load. sorry for being vague, but this is all that i know. somebody with
better knowledge of dlopening and kde influence on that will be better
able to answer the question.

renchi
---

I still think the answer is the usage of libltdl (and maybe KDE).
But it's too late now to check the docs in the web.

Hope this helps at least a little bit,
Achim
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>