[Digikam-users] Exiv2 library missing???

[Daniel Bauer]

On Wednesday 06 December 2006 23:06, Thorsten Schnebeck wrote:
> Am Mittwoch 06 Dezember 2006 18:19 schrieb Daniel Bauer:
> > On Wednesday 06 December 2006 18:12, Thorsten Schnebeck wrote:
> > > [...]
> > >
> > > What is the content of  /home/digi/digikamSVN/bin/exiv2-config?
> >
> > this: http://www.daniel-bauer.com/test/exiv2-config.txt
>
> ok, this is 0.12 and what I expected.
> So I looked into the check of ./configure
>
> first there is a test for exiv2-config this results to:
> "checking for exiv2-config... /home/digi/digikamSVN/bin/exiv2-config"
>
> This is the correct version. To help configure you could also use the
> env-variable $EXIV2_CONFIG but its not necessary.
>
> But now ./configure does not make anything useful with exiv2-config (like
> checking the version). No, instead it uses now pkg-config to check the
> version of exiv2.
>
> That check results to
> "checking for exiv2 >= 0.12... no"
>
> Question stays what overwrites your PKG_CONFIG_PATH?
>
> [search mode]
> #------------------------------------------------------------------
> # KIPI support (KDE Image Plugin Interface)
> #------------------------------------------------------------------
>
> if test "$PKGCONFIGFOUND" = "yes" ; then
>    # check for libkipi
>    have_libkipi=no
>
>    PKG_CONFIG_PATH="$prefix/lib${kdelibsuff}/pkgconfig:$PKG_CONFIG_PATH"
>    if test "$prefix" != "$kde_libs_prefix"; then
>        PKG_CONFIG_PATH="$kde_libs_prefix/lib${kdelibsuff}/pkgconfig:
> $PKG_CONFIG_PATH"
>    fi
>    export PKG_CONFIG_PATH
>
> ups - thats bitter! kipi check is before exiv2 test. THAT kills your global
> enviroment (and I think this is bad style and a BUG)
>
> With current configure checks you can only use ONE global exiv2 lib.
>
> Can you try this hack:
> Please change these lines of your digikam build script from
>
> make -f Makefile.cvs
> ./configure --prefix=$DIGIKAMDEST
> --with-extra-includes=$DIGIKAMDEST/include
> --with-extra-libs=$DIGIKAMDEST/lib make -j 4
>
> into:
>
> make -f Makefile.cvs
> PKGCONFIGFOUND="no" ./configure --prefix=$DIGIKAMDEST
> --with-extra-includes=$DIGIKAMDEST/include
> --with-extra-libs=$DIGIKAMDEST/lib make -j 4
>
> and tell us what configure now tells about the exiv2 check.
>
> Bye
>
>   Thorsten
>
Hi, good morning :-)

using PKGCONFIGFOUND="no" makes configure complain about other missing parts:

config.status: executing depfiles commands

-- digiKam configure results -------------------
-- sqlite3 found.................. NO

digiKam needs sqlite3. You need to install sqlite3 3.x, e.g. from
http://www.sqlite.org

-- libgphoto2 found............... YES
-- libkipi found.................. NO

digiKam needs libkipi. You need to install libkipi first
libkipi website is at http://extragear.kde.org/apps/kipi

-- libtiff found.................. YES
-- libpng found................... YES
-- lcms found..................... YES
-- Exiv2 library found............ YES
------------------------------------------------

-- digiKamImagePlugins configure results --------
-- digiKam found.................. YES
-------------------------------------------------

Now that it finds Exiv2 it doesn't find sqlite and libkipi anymore...
I guess, the above is the part of the output you're interested in, but the 
complete output is here:
http://www.daniel-bauer.com/test/compile_digikam.Thorsten.out.txt

btw.:
just to be sure I havn't lost sqlite/kipi somewhere, I run the script again 
after removing PKGCONFIGFOUND="no" again - and then sqlite/kipi is found, but 
Exiv2 not. So I guess you are on the right way, Thorsten, but the command 
must somehow be refined to affect the Exiv2 stuff only...

regards

Daniel
-- 
Daniel Bauer photographer Basel Switzerland
professional photography: http://www.daniel-bauer.com
Madagascar special: http://www.sanic.ch