[Digikam-users] bugs and wishes review

[Arnd Baecker]

Gilles and Jakob,

maybe I was wrong with my statement that
this is not a digikam issue...

Jakub, just to try to clarify the confusion which I may have created:
- For the step
  svn co  svn://anonsvn.kde.org/home/kde/branches/extragear/kde3/libs/
  cd libs
  make -f Makefile.cvs
  ./configure --prefix=$DIGIKAMDEST --with-extra-includes=$DIGIKAMDEST/include --w
ith-extra-libs=$DIGIKAMDEST/lib

  What is the output at the end of configure?

- What is the output of the corresponding configure step for digikam?
  svn co -N svn://anonsvn.kde.org/home/kde/branches/extragear/kde3/graphics/
  cd graphics
  svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin

  make -f Makefile.cvs
  ./configure -prefix=$DIGIKAMDEST --with-extra-includes=$DIGIKAMDEST/include --wi
th-extra-libs=$DIGIKAMDEST/lib


Independent of this, did you succeed  last night?

Best, Arnd




On Mon, 4 Jun 2007, Jakob Oestergaard wrote:

> Arnd Baecker wrote:
> > Hi Jakob,
> >
>
> Hi Arnd,
>
> ...
> >
> > I always install to a separate place,
> > following the instructions under
> > "Install digiKam in your Home Directory"
> > http://www.digikam.org/?q=download/svn
>
> That's exactly what I wanted to do (and *almost* did)  :)
>
> >
> > And, yes there is a problem when an old exiv2 (etc.) lies around,
> > see this message:
> > http://mail.kde.org/pipermail/kde-imaging/2007-May/005106.html
> > I have no idea if there are any plans to do anything on this.
> >
> > Also, this is a kde-imaging issue (not digikam ;-).
> > Maybe you could file a bug report there?
>
> I would say that it is a pkg-config bug. The tool attempts to do
> something but doesn't do it well (why use a pkg config path and not the
> linker path when resolving library versions?  that seems totally broken
> to me, unless I am missing something))
>
> > A temporary solution I use for myself is a small script which
> > modifies the configure script for kde-imaging, see below
> > (did not quite work last time, I had to change a few
> > ones like this manually, but you will get the idea).
>
> I'll try that workaround tonight. Thanks!
>
>