Re: Compiling from source on Windows fails to find DLLs

On Sun, 22 Oct 2017, Casper Gripenberg wrote:

> I compiled GraphicsMagick-1.3.26-windows-source with Visual C++
> according to the instructions in INSTALL-windows.html.
>
> But now when I try to run for example the analyze.exe demo,
> I get this:
>
>> analyze.exe lena.jpg
> Magick: Unable to load module
> ("C:\Program Files\File Viewer Lite\lib\magick\modules\
> coders\IM_MOD_RL_JPEG_.dll: The specified procedure could
> not be found.") reported by ..\..\magick\module.c:1485 (OpenModule)
>
> What has File Viewer Lite got to do with GraphicsMagick, and why
> is it looking for modules there?

I would guess that "File Viewer Lite" is partially based on 
GraphicsMagick and so it has provided its own GraphicsMagick 
installation, perhaps updating the Windows search path and setting the 
Windows registery entries documented in the "INSTALL-windows.html" 
text.  It might also have set other environment variables system-wide. 
These are causing your GraphicsMagick build to try to use the modules 
installed by "File Viewer Lite".

> I also tried setting MAGICK_HOME, but to no avail :(
>
> What's going on? Why can't GraphicsMagick find its own DLLs,
> even though they are all right there in the bin folder?

This does seem annoying.  The most powerful setting is 
'UseInstalledMagick' in magick_config.h.  Normally this should be left 
undefined.  If you have defined it, then correct operation is not 
assured unless the software has been "installed" using Windows 
registery entries.

Bob
-- 
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot