On Sat, Apr 11, 2015 at 09:34:11PM +0200, Jernej Simončič wrote:
The problem here is that while gimp.exe and it's libraries are in
bin\, the plugins are in lib\gimp\2.0\plug-ins\. GIMP does set the
environment to have bin\ directory in PATH, but if there's a DLL with
the same name as one used by plug-ins in System32, it'll take
precedence (DLL search order on Windows is executable directory,
System32 [SysWOW64 for 32-bit programs on 64-bit Windows], System,
Windows, current directory, %PATH%).
GIMP plug-ins are regular programs not DLLs, and they are executed by
GIMP. You can check the paths to these in the pluginrc that is typically
stored in %appdata%\Roaming.
The DLLs that these plug-in programs require are located in the bin
directory.
I suspect that this person has not set PATH. For example, the nightly
builds from darkrefraction.com just extract the tree of files and expect
a user to run the run_gimp.bat batch file (which sets PATH). If one
were to run gimp-2.9.exe directly in this case, the plug-ins that link
to DLLs would not find them (e.g., the file format ones that look for
libpng, libtiff, libjpeg, etc.).
The regular Windows installer sets this up, so you may want to ask that
person which installer was used.
Mukund
pgpITyxiUI1Jh.pgp
Description: PGP signature
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list