[Digikam-users] Import issue on SVN version

[Arnd Baecker]

Hi Dotan,

On Sun, 13 Jul 2008, Dotan Cohen wrote:

> Well, I've tried every combination of setting and not setting every
> variable that I could. I cannot get Digikam to show pictures, I always
> get a different error accompanied by "klauncher said: Unknown protocol
> 'digikamalbums'". I have tried running "update-desktop-files" as
> suggested here (http://lists.alioth.debian.org/pipermail/pkg-kde-extras/2005-December/000383.html).
> I don't see anything related to digikam in .xsession-errors, which was
> suggested in several pages that I found.
>
>
> Should I recompile without using prefixes? I have read here
> (http://mlblog.osdir.com/kde.digikam.user/2006-06/index.shtml#00010)
> that might help. According to here
> (http://mail.kde.org/pipermail/digikam-users/2005-November/000615.html)
> I have not set properly the kde install path. How should one know what
> that path is? If I don't use prefixes, then will Digikam find it
> automatically in compilation?

Not sure, the whole kio-slave stuff used to cause me a lot of
trouble in the past. Recently I somehow luckily got around problems ....

Just in case: the paths I set are
IGIKAM4DEST=/home/abaecker/NBB/SOFTWARE/DEV_digikam4
export PATH=/usr/lib/kde4/bin/:$PATH

export LANG=C
export KDEDIRS=$DIGIKAM4DEST:/usr/lib/kde4/
export LD_LIBRARY_PATH=$DIGIKAM4DEST/lib:$LD_LIBRARY_PATH
export LDPATH=$DIGIKAM4DEST/lib:$LDPATH
export PATH=$DIGIKAM4DEST/bin:$PATH
export PKG_CONFIG_PATH=$DIGIKAM4DEST/lib/pkgconfig

export MARBLE_PATH=$HOME/NBB/SOFTWARE/Marble/
export LD_LIBRARY_PATH=$MARBLE_PATH/lib:$LD_LIBRARY_PATH
export LDPATH=$MARBLE_PATH/lib:$LDPATH
export PATH=$MARBLE_PATH/bin:$PATH
export PKG_CONFIG_PATH=$MARBLE_PATH/lib/pkgconfig:$DIGIKAM4DEST/lib/pkgconfig
export INCLUDE_DIR=$MARBLE_PATH/include:$INCLUDE_DIR

export CMAKE_INCLUDE_PATH=$MARBLE_PATH/include:$DIGIKAM4DEST/include
export CMAKE_LIBRARY_PATH=$MARBLE_PATH/lib:$DIGIKAM4DEST/lib

(Several of them only needed during compile .. ;-)

Maybe running
  /usr/lib/kde4/bin/kdeinit4
would help (in contrast to 0.9.x I never had to do that for 0.10,
but maybe I was just lucky ...).

Hmm, but now I am running of ideas ...

Best, Arnd