<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
From your paste:<br>
<blockquote>Could NOT find Exiv2<span class="sy0">:</span> Found
unsuitable version <span class="st0">"0.25.0"</span><span
class="sy0">,</span> but required is at least <span class="st0">"0.26"</span>
<span class="br0">(</span>found <span class="sy0">/</span>usr<span
class="sy0">/</span>lib<span class="sy0">/</span>x86_64<span
class="sy0">-</span>linux<span class="sy0">-</span>gnu<span
class="sy0">/</span>libexiv2.<span class="me1">so</span><span
class="br0">)<br>
</span></blockquote>
You probably have the system exiv2 package still installed.<br>
<br>
<div class="moz-cite-prefix">On 26/06/2019 15:41, woenx wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1561556517492-0.post@n4.nabble.com">
<pre class="moz-quote-pre" wrap="">Thank you Gilles,
I've been so far unable to compile it so digikam's bootstrap.linux script
detects it.
The steps I followed were:
1) Download the last release of exiv2 (0.27.1) from github.
<a class="moz-txt-link-freetext" href="https://github.com/Exiv2/exiv2/releases/tag/0.27.1">https://github.com/Exiv2/exiv2/releases/tag/0.27.1</a>
2) Uncompress the tar.gz file, and copy the bootstrap-exiv2.linux.sh script
to the main exiv folder (where CMakeLists.txt is).
3) Run './bootstrap-exiv2.linux.sh'
4) Enter the build directory, and run 'cmake --build .'
5) 'sudo make install'
6) I update the PATH (as instructed in their github page): 'export
PATH="/usr/local/bin:$PATH" && export
LD_LIBRARY_PATH="/usr/local/lib:$LD_LIBRARY_PATH"'
Exiv's 2 seems to compile without errors, and I can run the exiv2 command in
the terminal.
digikam@digikam-VirtualBox:~/digikam$ exiv2 --version
exiv2 0.27.99.0
However, when I try to compile digikam (the lastest version from github),
libexiv2 cannot be found:
<a class="moz-txt-link-freetext" href="https://pastebin.com/xQsfWwHb">https://pastebin.com/xQsfWwHb</a>
Is libexiv2 a separate package from exiv2?
I am a bit lost at the moment, and I am not sure how to check if the
PKGConfig files are correctly created after compiling exiv2. These are the
files related to exiv2 I find using the locate command:
<a class="moz-txt-link-freetext" href="https://pastebin.com/TXTkAa3q">https://pastebin.com/TXTkAa3q</a>
Any advise or guidance would be greatly appreciated!
Gilles Caulier-4 wrote
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Le mar. 25 juin 2019 à 14:48, woenx <
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">marcpalaus@
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">> a écrit :
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">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
<a class="moz-txt-link-freetext" href="https://www.digikam.org/download/git/">https://www.digikam.org/download/git/</a>,
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.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
0.27 is highly recommended.
The detection of library is in this cmake script :
<a class="moz-txt-link-freetext" href="https://cgit.kde.org/digikam.git/tree/core/cmake/modules/FindExiv2.cmake">https://cgit.kde.org/digikam.git/tree/core/cmake/modules/FindExiv2.cmake</a>
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 :
<a class="moz-txt-link-freetext" href="https://cgit.kde.org/digikam.git/log/project/scripts/bootstrap-exiv2.linux.sh">https://cgit.kde.org/digikam.git/log/project/scripts/bootstrap-exiv2.linux.sh</a>
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
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
--
Sent from: <a class="moz-txt-link-freetext" href="http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html">http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html</a>
</pre>
</blockquote>
<br>
</body>
</html>