[Kde-imaging] exiv2 (Re: extragear/libs/kipi-plugins)

Fabien fabien.ubuntu at gmail.com
Mon Dec 4 14:44:54 CET 2006


Hi,

Gilles Caulier wrote:
> On Wednesday 29 November 2006 15:10, Angelo Naselli wrote:
> 
>>Alle 14:47, mercoledì 29 novembre 2006, Gilles Caulier ha scritto:
>>
>>>On Wednesday 29 November 2006 14:45, Angelo Naselli wrote:
>>>
>>>>Alle 13:55, mercoledì 29 novembre 2006, Gilles Caulier ha scritto:
>>>>
>>>>>On Wednesday 29 November 2006 13:26, Angelo Naselli wrote:
>>>>>
>>>>>>Alle 12:37, mercoledì 29 novembre 2006, Gilles Caulier ha scritto:
>>>>>>
>>>>>>>On Wednesday 29 November 2006 12:31, Gilles Caulier(UNTRUSTED,
>>>>>>>sender is
>>>>>>>
>>>>>>><kde-imaging-bounces-+caulier.gilles=kdemail.net-RoXCvvDuEio at public.gmane.org>) wrote:
>>>>>>>
>>>>>>>>On Wednesday 29 November 2006 00:17, Angelo Naselli wrote:
>>>>>>>>
>>>>>>>>>Ok, I added libexiv 0.12 requirement.
>>>>>>>>>It's too late to go on releasing now, sorry I'll try
>>>>>>>>>tomorrow.
>>>>>>>>>
>>>>>>>>>Anyway I had to backport libexiv since It isn't in mdv 2007,
>>>>>>>>>do we really believe it's correct to cut off a lot of users
>>>>>>>>>since libexiv 0.12 is not everywhere?
>>>>>>>>>
>>>>>>>>>Another problem, changing libexiv release configure fails
>>>>>>>>>but it seems to allow to compile anyway. Gilles I didn't
>>>>>>>>>change if test "x$have_exiv2" != "xyes"; then
>>>>>>>>>     DO_NOT_COMPILE="$DO_NOT_COMPILE kipi-plugins"
>>>>>>>>>fi
>>>>>>>>>
>>>>>>>>>Do you know why it goes on?
>>>>>>>>>
>>>>>>>>>Col, yes pkg-config was important and Gilles I used
>>>>>>>>>exiv2-config instead of a test on hpp file.
>>>>>>>>>
>>>>>>>>>Please test it.
>>>>>>>>
>>>>>>>>It doesn't work.
>>>>>>>>
>>>>>>>>I have uninstalled Exiv2 0.12 on my computer and installed 0.11
>>>>>>>>release instead. Exiv2 0.11 is detected like the right version
>>>>>>>>to use...
>>>>>>
>>>>>>Odd, can you post the
>>>>>>cat /usr/lib/pkgconfig/exiv2.pc of both 0.11 and 0.12?
>>>>>>
>>>>>>Angelo
>>>>>
>>>>>exiv2.pc from Exiv2 0.11
>>>>
>>>>Gilles I believe you should make -f Makefile.cvs first ;)
>>>
>>>no, "make config" with Exiv2. Done in boh case.
>>
>>hmm Gilles here is my test:
>>checking for gphoto2-config... /usr/bin/gphoto2-config
>>checking for gphoto2-port-config... /usr/bin/gphoto2-port-config
>>checking for xslt-config... /usr/bin/xslt-config
>>checking for exiv2-config... /usr/bin/exiv2-config
>>checking for pkg-config... /usr/bin/pkg-config
>>checking for exiv2 >= 0.12... yes
>>checking EXIV2_CFLAGS...
>>checking EXIV2_LIBS... -lexiv2
>>checking for libgpod-1.0 >= 0.4.0... no
>>configure: WARNING:
>>          libgpod is required for the iPod export plugin.
>>checking for Qt with OpenGL support... yes
>>
>>and here is it yours (from your previous mail):
>>checking for exiv2-config... /usr/bin/exiv2-config
>>checking exiv2/exif.hpp usability... yes
>>checking exiv2/exif.hpp presence... yes
>>checking for exiv2/exif.hpp... yes
>>checking for pkg-config... /usr/bin/pkg-config
>>checking for libgpod-1.0 >= 0.4.0... no
>>configure: WARNING:
>>          libgpod is required for the iPod export plugin.
>>checking for Qt with OpenGL support... yes
>>
>>As you can see your configure is testing exiv2/exif.hpp.
>>That test was the old one, it isn't done any more.
>>So I guess you forgot to re-build your configure, e.g.
>>make -f admin/Makefile cvs (or make -f Makefile.cvs),
>>but I maybe wrong.
>>
>>Angelo
> 
> 
> ok. Work fine now. Look the results:
> [...] 

Using my script (compile_digikam.txt
http://www.digikam.org/?q=download/svn), it doesn't work (exiv2 is
installed in a non-default directory).

I had to use "export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig" to make
it work.

Is it normal or should the configure script also check for exiv2.pc in
the right directory depending on the given prefix (or
--with-extra-includes) ?

--
Fabien


More information about the Kde-imaging mailing list