[Digikam-users] Exiv2 library missing???

[Fabien]

Hi,

Thorsten Schnebeck wrote:
> Am Mittwoch 06 Dezember 2006 18:19 schrieb Daniel Bauer:

 > [...]

> 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)

Well done Thorsten, I missed this part...

This part is added because there's a check for KIPI that uses 
KDE_PKG_CHECK_MODULES.

It's defined there :
<http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/acinclude.m4.in?rev=584244&view=markup>

I wonder why they don't put the original $PKG_CONFIG_PATH first, before 
adding the $kde... stuff.


If I replace KDE_PKG_CHECK_MODULES by PKG_CHECK_MODULES, it will remove 
the PKG_CONFIG_PATH. This is the diff between both configure :

<
<  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
<


so, it would be ok... But I don't know if there can be some side effects 
about that.

--
Fabien