<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.30.3">
</HEAD>
<BODY>
Hy everybody, I'm back at Square One: DigiKam 1.8 runs with exiv2 .19 and my Nikon cringes when it gets near the computer. <BR>
<BR>
I have to compile my own DigiKam once again. Can't do it. Nope, nyet, nada, nein, non.<BR>
<BR>
Yeah, I've tried to follow the instructions so graciously provided to me in December. However, this doesn't give me any joy whatsoever. The links in the earlier instructions are now dead ends. For example, I can't find the libexiv2 debs. Can somebody hold my hand and take me through this morass once again, please?<BR>
<BR>
* I've learned that DigiKam is very well-known for two things: The excellent functionality of the program and, the non user-friendly horrendous hoops of blazing fire that people must jump through in order to compile it and its many dependencies. My contemporaries and I anxiously await the day that some decent, full compiling instructions along with current links will finally be made available.<BR>
<BR>
On Mon, 2010-12-20 at 16:33 +0100, Photonoxx wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Le Sun, 19 Dec 2010 18:36:53 +0100, Mark Greenwood
<<A HREF="mailto:captain_bodge@yahoo.co.uk">captain_bodge@yahoo.co.uk</A>> a écrit:
> Some hints for Ubuntu users:
>
> sudo apt-get build-dep digikam (installs all dependencies for building
> digikam)
>
> apt-get source digikam (gets the source code for the ubuntu digikam
> package - easiest thing to do if all you want to do is rebuild it
> against a new library)
> dpkg-buildpackage -rfakeroot -uc -b (builds the .deb package from the
> source you just retrieved)
>
> sudo add-apt-repository ppa:philip5/extra
> sudo apt-get update
> sudo apt-get upgrade (sets up a repository with, amongst other
> things, the latest and greatest digikam and kipi-plugins)
>
> All found via Google. Happy holidays ;-)
Can you confirm you post here two different hint (the one with
dpkg-buildpackage and the other with PPA).
Inspired by this, I found way simpler way two get evix2 0.20 working with
Digikam.
At least you have to pass by a compile step, but don't have to compile
Digikam. May be it's a little late for Hevï Guy...
If more technician could validate this method, it would be nice.
First of all I download exiv2 deb packages from natty repository on
Launchpad.
I think the needed packages are mostly Libexiv2-9 and libexiv2-dev
<A HREF="https://launchpad.net/ubuntu/natty/+package/libexiv2-9">https://launchpad.net/ubuntu/natty/+package/libexiv2-9</A>
<A HREF="https://launchpad.net/ubuntu/natty/+package/libexiv2-dev">https://launchpad.net/ubuntu/natty/+package/libexiv2-dev</A>
For each URL you still have to select which published version you need
(32bits or 64bits ?) and click on the deb link in the new page (under
"downloadable item...")
With this deb you can install Libexiv2-9 and libexiv2-dev
After that, you just have to recompile you libkexiv2-8 that is used by
Digikam.
To do that, I make this in an appropriate folder for exemple src:
mkdir src
cd src
sudo apt-get build-dep libkexiv2-8
apt-get source libkexiv2-8
cd kdegraphics[you-version, just look the name of the created folder]
dpkg-buildpackage -rfakeroot -uc -b
This last command take a quite long time because I don't knows how to only
generate the deb for libkexiv2, and the command line generate packages for
all the kdegraphics components. but at the end, in the src directory,
you'll get all the generated deb files.
Now, there just stay to install libkexiv2-8[your-version].deb file.
Double-clicking on it to open software-center give me some trouble. In
fact, when I click on "reinstall" button, Software-center says Digikam and
some other software have to be uninstalled to reinstall libkexiv2-8
package, and so, I decided to install gdebi software and Just have to make
a right click on libkexiv2-8.*.*.deb and choosing "open with gdebi...",
and reinstall work without alert.
Launching Digikam give me now exiv 0.20 in component info.
If someone, more expert than me, could confirm there's no matter with this
way...
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>