[Digikam-devel] Working environment

[Arnd Baecker]

Hi Pawel,

On Sat, 24 Nov 2007, [UTF-8] PaweÅ^B Marciniak wrote:

> Arnd Baecker wrote:
>
> >> > But when I try to run the svn
> >> > version of digiKam (even after make install), the kio_* stuff it
> >> > depends upon, needs exiv2 globally installed in order to work.
> >
> > This shouldn't be the case. Did you also remove
> > the kexiv2 stuff before installing?
> > (I think this is also necessery ...)
>
> I did remove both.
>
> >> My concern is that
> >> > perhaps I misconfigured something, so that the dev version still runs
> >> > the stable versions of its libraries, maybe even libdigikam is used
> >> > from the stable version and then debugging would be kinda hard then ;)
> >> >
> >> > My env (kept that way all the time from the time of checkout):
> >> > KDEDIR="/home/pave/digikam_svn/installed"
> >> > KDEDIRS="/home/pave/digikam_svn/installed"
> >> > LDPATH="/home/pave/digikam_svn/installed/lib:"
> >> > LD_LIBRARY_PATH="/home/pave/digikam_svn/installed/lib:"
> >> >
> PATH="/home/pave/digikam_svn/installed/bin:/bin:/usr/bin:/usr/X11R6/bin:\
> >> > /opt/bin:/opt/kde/bin:/opt/qt/bin"
> >> > PKG_CONFIG_PATH="/home/pave/digikam_svn/installed/lib/pkgconfig"
> >> > UNSERMAKE="no"
> >>
> >> I just noticed something strange! An excerpt from ldd
> >> kio_digikamalbums.so (the svn version):
> >> [...]
> >> libkexiv2.so.3 => /opt/kde/lib/libkexiv2.so.3 (0xb7a3f000)
> >> [...]
> >> libexiv2.so.2 => /home/pave/digikam_svn/installed/lib/libexiv2.so.2
> >> (0xb779f000)
> >> [...]
> >>
> >> How come?
> >
> > Hmm, I am puzzled as well, all paths look fine to me
> > (though I normally use
> > export DIGIKAMDEST=/tmp/DEV_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
> >
> > i.e., I add the "original" paths via :$PATH etc...)
> >
> > The only idea I have:
> > Did you do run kbuildsycoca after setting the environment variables?
>
> No I didn't (the website doesn't mention that).
On http://www.digikam.org/?q=download/svn
running `kdeinit` is mentioned, but it seems that kbuildsycoca
is enough


> Now I did and it seems that
> it solved the problem with wrong libs (however, I'm not sure if that was
> the only reason). Thanks for this tip!
>
> Despite now linking to correct libs, the kio_* stuff still doesn't work. I
> uninstalled the stable digiKam to be sure that the svn kio_* are used and
> after starting digiKam I get:
> kio (KMimeType): WARNING: KServiceType::offers : servicetype
> Digikam/ImagePlugin not found
> kio (KMimeType): WARNING: KServiceType::offers : servicetype
> Digikam/ImagePlugin not found
> digikam: ERROR: : couldn't create slave : Unable to create io-slave:
> klauncher said: Unknown protocol 'digikamdates'.
> digikam:
> digikam: WARNING: [void Digikam::AlbumManager::slotResult(KIO::Job*)] Failed
> to list dates
> digikam: ERROR: : couldn't create slave : Unable to create io-slave:
> klauncher said: Unknown protocol 'digikamalbums'.
> digikam:
> digikam: WARNING: Failed to list url: Could not start process Unable to
> create io-slave:
> klauncher said: Unknown protocol 'digikamalbums'.

Hmm, maybe things got screwed, because on compile
it did find the old libs?
Maybe you start from the beginning again?
(And yes, we should mention this somewhere on the above page ...)

> > Concerning the time-difference and IRC: you are not in Poland
> > currently, as your e-mail might suggest? ;-)
>
> I'm still in Poland, but only for the next 5 days, then I'm moving behind
> the ocean :)

Well, that will cause some time-shift ...
(On the other hand we work 24/7 on digikam and are online
all the time ... just kidding ..., still there might be sufficient
overlap ...)

Best, Arnd