[Digikam-users] Digikam 0.10 - dcraw dependancy?
caulier.gilles at gmail.com
Mon Aug 11 20:25:35 BST 2008
2008/8/11 Константин Маслов <conma at yandex.ru>:
> В сообщении от Monday 11 August 2008 14:00:09 digikam-users-request at kde.org
>> Message: 1
>> Date: Sun, 10 Aug 2008 12:46:08 +0200
>> From: Mikolaj Machowski <mikmach at wp.pl>
>> Subject: Re: [Digikam-users] Digikam 0.10 - dcraw dependancy?
>> To: digikam-users at kde.org
>> Message-ID: <200808101246.08602.mikmach at wp.pl>
>> Content-Type: text/plain; charset="iso-8859-2"
>> Dnia Sunday 10 of August 2008, ?????????? ?????? napisa?:
>> > Hi.
>> > I've just build kde4.1 for testing, more digikam then kde itself.
>> > New shiny digikam did not open my NEFs, neither in preview nor in edit
>> > mode. Shortly I discover that I have libkdcraw installed but I have no
>> > dcraw on my system :)
>> > So the question is:
>> > Is it right that digikam and libkdcraw not depend on dcraw?
>> Yes. Kdcraw have dcraw "inside".
> Is it?
> I just built brand new KDE4, build Digikam 0.10-beta2 from kdesvn Gentoo
> overlay. Digikam did not open my nefs. Libkdcraw was on the system, dcraw was
> not, I did not check if they have kdcraw ebuild and if it was installed.
> Digikam worked fine with or without dcraw. Without dcraw it just write "I
> cann't open such type of image" but no errors or crashes.
> Then I built dcraw (not kdcraw, just dcraw) and Digikam opened my nefs.
> I checked it right now, there is no kdcraw ebuild in portage, only
no. kdcraw is just the name of dcraw binary program build in
libkdcraw. it's include in this library.
> libkdcraw-4.1.0. Libkdcraw ebuild depends only on media-libs/jpeg and
> media-libs/lcms, not on dcraw.
> So I wonder if it is normal such absence of dependancy?
See my comment before.
> And, if it is ok,
> perhaps make the message little more informative? Something like "I cann't
> open this image because you have no dcraw on your box"?
kdcraw program availability is always tested at digiKam startup and a
warning dialog is open to bring user.
So the problem is outside...
More information about the Digikam-users