Please tell me how to compile digikam with exiv2 and kdcraw libraries

[Jens Müller-10]

>It's kdelibs loading the ioslave files. Nothing we care at all about in our
>code, just create a job with a digikamalbums:/ URL and KDE does everything for
>us. I can imagine that kdeinit will only look in standard KDE directories,
>unless you tell it to look elsewhere.
>
>Why not install digikam in standard KDE places?

Shure, that is one solution, at least for developers.

But I know some people, who don't want to mess their packagemanagement with own compiled stuff and don't want to run in trouble when something is broken in svn (see latest database problems). Therefore I created the svnalongstable howto on download page.
I think that there some people who want to test latest svn features (and report bugs), but don't want to risk loosing their information from their huge image database. So I'm interested in any information making this howto better.

Regards, Jens
___________________________________________________________
GRATIS: Movie-Flat mit über 300 Top-Videos. Für WEB.DE Nutzer
dauerhaft kostenlos! Jetzt freischalten unter http://movieflat.web.de
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Martin Klapetek]

On Thu, May 20, 2010 at 12:59, Jens Müller <[hidden email]> wrote:

>It's kdelibs loading the ioslave files. Nothing we care at all about in our
>code, just create a job with a digikamalbums:/ URL and KDE does everything for
>us. I can imagine that kdeinit will only look in standard KDE directories,
>unless you tell it to look elsewhere.
>
>Why not install digikam in standard KDE places?

Shure, that is one solution, at least for developers.

But I know some people, who don't want to mess their packagemanagement with own compiled stuff and don't want to run in trouble when something is broken in svn (see latest database problems). Therefore I created the svnalongstable howto on download page.
I think that there some people who want to test latest svn features (and report bugs), but don't want to risk loosing their information from their huge image database. So I'm interested in any information making this howto better.

Regards, Jens

Yeah, that's my case :) I'd like to keep the stable version around. There seems to be something wrong with 64bit distro paths, I'll try to play little more with the env vars, but I'm open for any other idea ;)

Marty

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

[Marcel Wiesweg]

> > Shure, that is one solution, at least for developers.
> >
> > But I know some people, who don't want to mess their packagemanagement
> > with own compiled stuff and don't want to run in trouble when something
> > is broken in svn (see latest database problems). Therefore I created the
> > svnalongstable howto on download page.
> > I think that there some people who want to test latest svn features (and
> > report bugs), but don't want to risk loosing their information from their
> > huge image database. So I'm interested in any information making this
> > howto better.

Given the process the ioslaves are started (protocol of URL -> lookup in
.desktop file -> starting of slave by kdeinit) I dont know how you could
install different ioslaves for a KDE installation. There may be a way to
always start the newly installed ioslaves, possibly by restarting kdeinit or
telling it in any other way to look in a different directory as well.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel