Bug 174690

Summary:	liblcms dll not found
Product:	[Unmaintained] kde-windows	Reporter:	Rainer Lay <rainer.lay>
Component:	installer	Assignee:	Christian Ehrlicher <Ch.Ehrlicher>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	ps_ml
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	issue with kdcraw.dll

Description Rainer Lay 2008-11-09 09:01:38 UTC

Version:           unknown (using 4.1.3 (KDE 4.1.3), MS Visual Studio 2005 SP1)
Compiler:          cl.exe
OS:                Microsoft Windows (i686) release 5.1 (XP Professional)

when starting digikam,  I get a message, that liblcms-1.dll is not found. I tried to install a seperate dll - wihtout success.

Comment 1 caulier.gilles 2008-11-09 09:16:31 UTC

It's not reproductible here. 

Are you set all env. variable in Win32 System control panel (KDEDIRS, KDEROOT, etc...) ?

Gilles Caulier

Comment 2 Rainer Lay 2008-11-09 09:58:53 UTC

I set KDEDIRS to c:\programme\kde, KDEROOT to %KDEDIRS% and add %KDEDIRS%\bin;%KDEDIRS%\lib to PATH.

thanx for your quick answer to far.

Comment 3 caulier.gilles 2008-11-09 10:02:45 UTC

And it doesn't work better ?

Are you installed liblcms package from KDE installer GUI ? Here it work fine...

Gilles Caulier

Comment 4 Patrick Spendrin 2008-11-09 11:47:29 UTC

The problem was a missing dependency when you installed digikam (I fixed this now).
As a hotfix just for you, get the package from: http://winkde.org/pub/kde/ports/win32/releases/stable/latest/lcms-1.17-bin.zip download it, and unpack it into your kde directory. Then it should work.

Comment 5 Rainer Lay 2008-11-09 13:46:44 UTC

the hotfix reveals an incompatibility with kdcraw.

Comment 6 Rainer Lay 2008-11-09 13:47:36 UTC

Created attachment 28436 [details]
issue with kdcraw.dll

Comment 7 Rainer Lay 2008-11-14 20:18:48 UTC

I installed lcms from the url above, which results in the mentioned kdcraw issue. I did an update some days later (today, kdelibs were updated) and the issue remained.

So this bug is not resolved for me.