[Digikam-devel] compile problems for digikam

[Mikolaj Machowski]

Dnia Saturday 26 of April 2008, Arnd Baecker napisał:
> Gilles, Marcel and everyone else:
> is there something which can be done to improve the situation?
>
> The main problems which seem to occur are
> (Not that the following is not written with any understanding/knowledge,
> but just an attempt at a summary):
> A) Different libexiv2 on the system seem to cause problems.
>    I just don't understand why?
>    If they are at separate places, and the paths are
>    set correctly, this should do no harm at all.

> B) The same with kexiv2, kdcraw, it seems
>    (not sure about libkipi, kipi-plugins)?

Better checking for version of kexiv2 (and exiv2 itself)? 
Configure scrips are checking only for regular version number eg. 0.16
while all this pieces are very actively developed and often newer
version of digiKam svn require specific svn versions of these two
elements - especially kexiv2.

AFAIK there is no direct dependency on libkipi. But libkipi and
kipi-plugins also depend on kdcraw and (k)exiv2.

> C) kioslave might not always be updated
>    (i.e. kdeinit or kbuildsycoca  might be needed)

Never had any problems with that.

> Is it possible to solve any of these issues?
>
> One simple diagnostic tool might be to print out
> the compile date  and time + svn revision + version
> of the pieces involved?
> (Would this be possible?)
>
> Are there better approaches?

More monolithic approach? Some svn "symlinks" which will cause automatic
update of libraries from extragear/libs ? KOffice was using that trick
to use kdgantt library from kdepim. Also admin directory in all KDE
modules is updated that way.

m.