[digiKam-users] Compiling digikam and exiv2

[Gilles Caulier]

Le mar. 25 juin 2019 à 14:48, woenx <marcpalaus at hotmail.com> a écrit :

> Hello,
>
> First of all, sorry if that has been answered somewhere else. I read other
> threads about compiling digikam in this mailing list, but I couldn't manage
> to do it myself.
>
> I am trying to compile digikam from source in an Ubuntu 18.04 installation,
> in order to create up to date .deb packages (and also be able to try myself
> the changes introduced by the GSoC2019). However, I seem to be experiencing
> some problems, especially regarding the exiv2 package.
>
> I start from a fresh ubuntu 10.04.2 LTS amd64 install in a virtual machine.
> I try to follow the instructions at https://www.digikam.org/download/git/,
> but the problem comes when ./bootstrap.linux can't find the exiv2 package
> installed.
>
> In theory, it needs exiv2 0.26 or newer (the lastest version in their
> repository seems to be 0.27). I first tried using the already compiled
> version of exiv2 and libexiv2-26 for debian (version 0.26-1), but Digikam's
> compilation script does not seem to detect them.
>

0.27 is highly recommended.

The detection of library is in this cmake script :

https://cgit.kde.org/digikam.git/tree/core/cmake/modules/FindExiv2.cmake

 Under Linux, the PKGConfig files are parsed to detect the library
installation. Sound like under Ubuntu this standard is not well respected
(another one, but you must know that i dislike this Linux box, and i wont
said i 'hate' ubuntu...).

To compile the Exiv2 library, look my script given here :

https://cgit.kde.org/digikam.git/log/project/scripts/bootstrap-exiv2.linux.sh

This one is optimized to only compile the minimum for digiKam and disable
the unstable code from the library. I compile current code from Exiv2,
where API have been broken for next 0.28. digiKam core have been fixed to
support this API (there is no API transition stage in Exiv2 (:=)))). As
Exiv2 API are strictly used in limited area in digiKam core, this limit the
maintenance to the minimum.
I see that another projects using Exiv2 are really perturbed by these
recent changes.

Best

Gilles Caulier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20190625/309f5304/attachment.html>