[Kde-imaging] problems with finding correct exiv2

[Arnd Baecker]

Hi,

it seems that either I posted the question/problem below
to the wrong mailing list, or no one can make
any sense out of what I wrote.

Could you maybe direct me to the right mailing list to
report this problem?

Best, Arnd

P.S.: Personally I don't have a real problem with this,
because I can easily write myself a small script
which does the replacement in the Makefile automatically,
but it might bite other users as well   ... ;-(

On Sat, 5 May 2007, Arnd Baecker wrote:

> Hi,
>
> I am not sure, if this is really the right mailing list,
> but hopefully it is not too far off ;-)
>
> When trying to compile kipiplugins, obtained via
>   svn co svn://anonsvn.kde.org/home/kde/trunk/extragear/libs
> configured via
>   make -f Makefile.cvs
>   ./configure --prefix=$DIGIKAMDEST \
>     --with-extra-includes=$DIGIKAMDEST/include \
>     --with-extra-libs=$DIGIKAMDEST/lib
> the wrong exiv2 is found:
> I have a 0.10 in /usr/
> and a self-compiled (0.14) in $DIGIKAMDEST, but
> only the first is found.
>
> As paths
> export DIGIKAMDEST=/home/NBB/digikam
> export KDEDIRS=$DIGIKAMDEST:/usr
> export LD_LIBRARY_PATH=$DIGIKAMDEST/lib:$LD_LIBRARY_PATH
> export LDPATH=$DIGIKAMDEST/lib:$LDPATH
> export PATH=$DIGIKAMDEST/bin:$PATH
> export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig
> are set.
>
> Fiddling around with the configure script, it
> turned out that changing the order of
> the definitions of PKG_CONFIG_PATH inside the script to
> PKG_CONFIG_PATH="$PKG_CONFIG_PATH:$prefix/lib${kdelibsuff}/pkgconfig"
> did solve the problem for me.
>
> Is there a better solution?
> (and, if not, maybe the above ordering should be the default
> so that alternative configurations are used instead
> of the usual ones?)
>
> Best, Arnd
>
>
> _______________________________________________
> Kde-imaging mailing list
> Kde-imaging at kde.org
> https://mail.kde.org/mailman/listinfo/kde-imaging
>
>