[Digikam-devel] compile problems for digikam

[Gilles Caulier]

2008/4/26 Gilles Caulier <caulier.gilles at gmail.com>:
> 2008/4/26 Arnd Baecker <arnd.baecker at web.de>:
>
> > Hi,
>  >
>  >  it seems that people really struggle hard installing digikam from svn.
>  >  This is, from my point of view, a substantial problem,
>  >  preventing possible contributors from even getting started.
>  >  It also prevents people from trying out current svn to
>  >  see if bugs got fixed; many just wait until
>  >  packages exist for their system ...
>  >
>  >  Most likely, there are many users which tried, failed,
>  >  and never reported back to us!
>  >
>  >  Needless to say, that such problems have wasted
>  >  already several hours, both on the users side and
>  >  on the side of the digikam team .... ;-)
>  >
>  >  Gilles, Marcel and everyone else:
>  >  is there something which can be done to improve the situation?
>  >
>  >  The main problems which seem to occur are
>  >  (Not that the following is not written with any understanding/knowledge,
>  >  but just an attempt at a summary):
>  >  A) Different libexiv2 on the system seem to cause problems.
>  >    I just don't understand why?
>  >    If they are at separate places, and the paths are
>  >    set correctly, this should do no harm at all.
>
>  Exiv2 0.14 has switched to libtool's -version-info versioning system.
>
>  I recommend to always use Exiv2 >= 0.14, else mixing a recent release
>  and a older one < 0.14 will introduce dysfunction.
>
>  It still other way to fix in Exiv2, to improve binary compatibility
>  for ex, using 'd' private internal classes for all private member. But
>  it's a huge work to do.
>
>
>
>   >  B) The same with kexiv2, kdcraw, it seems
>  >    (not sure about libkipi, kipi-plugins)?
>
>  There is no reason for kipi-plugins. it's not a shared lib.
>
>  For kexiv2, kdcraw, kipi, it certainly an auto-tools issue.
>
>
>  >  C) kioslave might not always be updated
>  >    (i.e. kdeinit or kbuildsycoca  might be needed)
>  >
>
>  Ah the kio-slaves. I'm currently fight against KDE4 under Mandriva
>  2008.1. Since i have updated my system, when i start digiKam 0.10.0
>  under KDE3, all kioslave are not able to find libdigikam.la and do not
>  start.
>
>  It's certainly a wrong env. settings.
>
>  It's the same for kioslave from digiKam 0.9.x
>
>  Gilles
>

Arnd,

For KDE4 with Mandriva 2008.1, there is a script named "k4" which
initialize all env. bash variable to be able to run a KDE4 application
under KDE3. Look the new env created :

[gilles at localhost ~]$ export > k1.txt
[gilles at localhost ~]$ k4
[gilles at localhost ~]$ export > k2.txt
[gilles at localhost ~]$ diff k1.txt k2.txt
2a3
> declare -x DBUSDIR="/opt/kde4"
18a20,24
> declare -x KDEDIR="/opt/kde4"
> declare -x KDEDIRS="/opt/kde4"
> declare -x KDEHOME="/home/gilles/.kde4"
> declare -x KDETMP="/home/gilles/tmp/gilles-kde4"
> declare -x KDEVARTMP="/var/tmp/gilles-kde4"
38a45
> declare -x LD_LIBRARY_PATH="/opt/kde4/lib:"
50c57
< declare -x PATH="/usr/bin:/bin:/usr/local/bin:/usr/X11R6/bin/:/usr/games:/usr/lib/qt4/bin:/home/gilles/bin:/usr/lib/qt4/bin"
---
> declare -x PATH="/usr/lib/qt4/bin:/opt/kde4/bin:/usr/bin:/bin:/usr/local/bin:/usr/X11R6/bin/:/usr/games:/usr/lib/qt4/bin:/home/gilles/bin:/usr/lib/qt4/bin"
57c64
< declare -x QTDIR="/usr/lib/qt3"
---
> declare -x QTDIR="/usr/lib/qt4"
59a67
> declare -x QT_PLUGIN_PATH="/opt/kde4/lib/kde4/plugins"

Something similar must be done to run properly a KDE3 application
under Gnome for ex.

Gilles