Diaa Sami wrote:
> Well, I found out the problem, it lies in the way the gimp gets
> installed on windows.
> for some reason, the installer doesn't place the dll's need by the
> gimp(including libglib-2.0-0.dll) into the %Windows%\System32 folder,
This is intentional. Blindly copying to system32 is the reason why most
Windows system are in such an inferior state.
> instead, it uses the key
> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\ in the
> registry to tell windows to use some paths for finding binaries when
> this executable is launched.
This is the right thing to do - this way, the DLLs are only used if a
program which needs them is launched, and otherwise don't interfere.
> also, seems that these paths aren't used when launching from the
> command-line.
And finally this is why Microsoft provide the 'start' command. Using
start gimp-2.2.exe
will add the App Paths entry to PATH, just like it is done when starting
GIMP from e.g. Explorer.
HTH,
Michael
--
The GIMP > http://www.gimp.org | IRC: irc://irc.gimp.org/gimp
Wiki > http://wiki.gimp.org | .de: http://gimpforum.de
Plug-ins > http://registry.gimp.org |
___
Gimp-user mailing list
Gimp-user@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
