[Kde-imaging] New libkipi 0.1.4

[Michael J Gruber]

Angelo Naselli venit, vidit, dixit 2006-05-17 10:43:
>> Fixing the libjpeg thing leaves you with a libgcrypt error, fixing that
>> with a libgpg-error.la. I seem to remember that with rc1, only libjpeg
>> gave trouble, the other two appeared with rc2.
> hmm, Achim do you think we've missed some library tests in configure.in.in?

I think that looks sane.

>> I'm attaching a fix for libtool which does the job for me, although it
>> is very ugly. I don't know where libtool gets the wrong dependency_libs
>> from, and why it inserts absolute paths to nonexisting libs. Might be a
>> Suse thing.
> libtool is not released with kipi so we can't do anything on that script,
> but you can try to force configure to use your LDFLAGS and C(XX)FLAGS
> to use your path first, setting up them. Did you try that?

Tried with LDFLAGS, CFLAGS, CXXFLAGS, CPPFLAGS, LD_LIBARRY_PATH and
KDEDIRS, even though --with-extra-libs and --with-extra-includes should
take care of that. The problem seems to be that some libs are installed
in /opt/kde3, but without the headers; for these packages I have libs
and headers in $HOME/{lib,include}. I noticed that configure picks up
libkexif from /opt/kde3, for example, even though it is installed
locally, too.

I guess most people will have either libs+includes globally or none
globally (and libs+includes locally), so my setup is not common (and not
my choice...).

Michael