Working environment

Hi,

I remember that I once came across a post/article that told how to configure
kdevelop for hacking digiKam. I cannot find it anymore, do any of you
remember where it was and could point me there?

I would like to setup kdevelop and environment variables so that I can
run/debug digiKam or kipi-plugins directly from kdevelop, without the need
to run make install. The thing is that I want the debugging apps to use the
svn versions of libs (kexiv2, kipi etc.) instead of the ones installed in
my system.

Thanks,
Pawel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

mercoledì 21 novembre 2007 alle 12:50, Paweł Marciniak ha scritto:

> Hi,
>
> I remember that I once came across a post/article that told how to configure
> kdevelop for hacking digiKam. I cannot find it anymore, do any of you
> remember where it was and could point me there?
>
> I would like to setup kdevelop and environment variables so that I can
> run/debug digiKam or kipi-plugins directly from kdevelop, without the need
> to run make install. The thing is that I want the debugging apps to use the
> svn versions of libs (kexiv2, kipi etc.) instead of the ones installed in
> my system.

As far as kipi-plugins concern just use the kipiplugins.kdevelop file released into libs directory

take care of changing the --prefix=$HOME/your/installation/path into configure option
and if you run from a konsole remember to set LD_LIBRARY_PATH as
$HOME/your/installation/path/lib:$LD_LIBRARY_PATH (or lib64) and
run kbuildsycoca.
Run your preferred host application...

HTH,
        Angelo

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Hi Pawel,

2007/11/21, Paweł Marciniak <[hidden email]>:

Hi,

I remember that I once came across a post/article that told how to configure
kdevelop for hacking digiKam. I cannot find it anymore, do any of you
remember where it was and could point me there?

... don't know this article...
 

I would like to setup kdevelop and environment variables so that I can
run/debug digiKam or kipi-plugins directly from kdevelop, without the need
to run make install.

You can debug digiKam directly in Kdevelop just after recompiling. But for plugins, if you recompile one tool, you need to re-install it. No other way.

I use Kdevelop everytime to hack and code... Just use my Kdevelop project on digikam/project folder... That all..

If you is interressed to more contribute to digiKam, i recommend you to join us on #digikam IRC channel ( freenode.net server). We are generally online on the evening (Europe time).

Also, like Arnd do, you can ask an account to KDE svn to commits your patch after validation by me or Marcel. I work like this Arnd, who learn (very fast) Qt/KDE development.

We need more and more contributor. KDE4 port is not yet complete and delayed to june 2008 (KDE4.1), and all help to maintain KDE3 branch is very appreciate.

I guide and help contributors who want to add new important features on KDE3 branch. But i'm focalized on KDE4 port and i backport all KDE3 fix to KDE4...

Best

Gilles

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Angelo Naselli wrote:

> mercoledì 21 novembre 2007 alle 12:50, Paweł Marciniak ha scritto:
>> Hi,
>>
>> I remember that I once came across a post/article that told how to
>> configure kdevelop for hacking digiKam. I cannot find it anymore, do any
>> of you remember where it was and could point me there?
>>
>> I would like to setup kdevelop and environment variables so that I can
>> run/debug digiKam or kipi-plugins directly from kdevelop, without the
>> need to run make install. The thing is that I want the debugging apps to
>> use the svn versions of libs (kexiv2, kipi etc.) instead of the ones
>> installed in my system.
> As far as kipi-plugins concern just use the kipiplugins.kdevelop file
> released into libs directory take care of changing the
> --prefix=$HOME/your/installation/path into configure option

But I don't want to install anything! I want to use the libs that get built
inside src subdirectories. That's my point.

> and if you run
> from a konsole remember to set LD_LIBRARY_PATH as
> $HOME/your/installation/path/lib:$LD_LIBRARY_PATH (or lib64)

That's what I do when I just run the alternative svn versions without
messing with my stable system installation - I install digiKam & libs in my
homedir and everything works. But, as mentioned above, I want something
different now.

> and run
> kbuildsycoca. Run your preferred host application...

Could you explain what running kbuildsycoca would do in such situation?

Thanks in advance,
Pawel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Arnd Baecker]

Hi Pawel,

On Wed, 21 Nov 2007, [UTF-8] Pawe�^B Marciniak wrote:

> Angelo Naselli wrote:
>
> > mercoledì 21 novembre 2007 alle 12:50, Paweł Marciniak ha scritto:
> >> Hi,
> >>
> >> I remember that I once came across a post/article that told how to
> >> configure kdevelop for hacking digiKam. I cannot find it anymore, do any
> >> of you remember where it was and could point me there?
> >>
> >> I would like to setup kdevelop and environment variables so that I can
> >> run/debug digiKam or kipi-plugins directly from kdevelop, without the
> >> need to run make install. The thing is that I want the debugging apps to
> >> use the svn versions of libs (kexiv2, kipi etc.) instead of the ones
> >> installed in my system.
> > As far as kipi-plugins concern just use the kipiplugins.kdevelop file
> > released into libs directory take care of changing the
> > --prefix=$HOME/your/installation/path into configure option
>
> But I don't want to install anything! I want to use the libs that get built
> inside src subdirectories. That's my point.
>
> > and if you run
> > from a konsole remember to set LD_LIBRARY_PATH as
> > $HOME/your/installation/path/lib:$LD_LIBRARY_PATH (or lib64)
>
> That's what I do when I just run the alternative svn versions without
> messing with my stable system installation - I install digiKam & libs in my
> homedir and everything works. But, as mentioned above, I want something
> different now.
>
> > and run
> > kbuildsycoca. Run your preferred host application...
>
> Could you explain what running kbuildsycoca would do in such situation?

Somehow this is necessary, so that all the newly built
stuff is found correctly (following the defined PATHs)
when running digikam.

Well, this is not really a profound answer, I just use it
and it works ... ;-).
Maybe someone else can explain it properly ...

Best, Arnd

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Gilles Caulier wrote:

> I would like to setup kdevelop and environment variables so that I can
>> run/debug digiKam or kipi-plugins directly from kdevelop, without the
>> need to run make install.
>
>
> You can debug digiKam directly in Kdevelop just after recompiling. But for
> plugins, if you recompile one tool, you need to re-install it. No other
> way.
>
> I use Kdevelop everytime to hack and code... Just use my Kdevelop project
> on digikam/project folder... That all..

I've been using digikam_svn.kdevelop project from digikam folder, and it's
working so I don't think there's a need to change to the digikam/project/
one, right?

There's one issue I want to ask about. I keep the svn versions in my
homedir, separate to globally installed stable versions. To properly
compile digiKam and libs against the svn-installed exiv2, I have to
temporarily uninstall stable exiv2 version from my system (the old known
recurring configure/make problem...). 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. 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"

> If you is interressed to more contribute to digiKam, i recommend you to
> join us on #digikam IRC channel (freenode.net server). We are generally
> online on the evening (Europe time).
>
> Also, like Arnd do, you can ask an account to KDE svn to commits your
> patch after validation by me or Marcel. I work like this Arnd, who learn
> (very fast) Qt/KDE development.

I'm also new to Qt/KDE development - but I figured out that reading digiKam
code (by hunting bugs) is a nice way to learn it :) I already requested the
svn access. However, I don't think I will be able to join you on IRC very
often - time difference.

Regards,
Pawel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Paweł Marciniak wrote:

> There's one issue I want to ask about. I keep the svn versions in my
> homedir, separate to globally installed stable versions. To properly
> compile digiKam and libs against the svn-installed exiv2, I have to
> temporarily uninstall stable exiv2 version from my system (the old known
> recurring configure/make problem...). 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. 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?

Pawel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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). 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'.
.

> 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 :)

Best,
Pawel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel