You are here

GIMP Resynthesizer Plug-In

I am trying to install the Resynthesizer Plug-In and make it part of the GIMP program. I need to remove the text from a picture I have of an animal in the ocean. When I click on the exe file of the Resynthesizer, I get the message that it does not work because the libgimp-2.0-0.dll is not found. How can this be fixed? I need to stress that I am not a techie and don't understand most of the terminology I have read on the blogs, so can someone explain it in layman's language, thank you.

I need to know how to fix the problem and how to download and install the Resynthesizer Plug-In and make it a part of the GIMP program.

I am using Windows Vista Home Basic Version 6.0., 32-bit system.

Thank you.

Judy Kunz
t_indo_merel@hotmail.com

A plugin doesn't work by merely clicking on it. Once it's properly installed, and Gimp is restarted, it appears as an additional menu entry somewhere in the Gimp menus (read the plugin documentation to know where)

Normally a simple plugin is installed by copyin,g it to the Gimp plugin directory (on Windows, something like "C:\Program Files\Gimp\lib\gimp/2.0\plug-ins). The resynthetizer may be a bit more complex to install, but it seems it comes with a dedicated installation program. Asking in the propoer thread could help: http://registry.gimp.org/node/25219.

Not sure if this fixes it, as this is common on Linux systems as well.
If you can find any libgimp-2???.dll copy it with the name libgimp-2.0-0.dll or put the libgimp-2.0-0.dll in with the rest of your windows' dlls. (i.e. C:\WINDOWS\system32) Hopefully its backwards compatible with the plug-in.
Many authors cross compile from linux systems for Windows and while not realizing they have done so, inadvertently already added the missing dll in the name state the app is looking for. What I have learned is, before one provides apps to the general public one should try their release on a bare Windows machine less they become a source inflamed.

This is about installing apps in general, both modern and ancient ways of doing it, with some specifics (but not all the details) for GIMP plugins. This is mainly for Windows users who have experienced only the modern ways. It is unfortunate that the ancient ways must still be explained, but Linux, and the world of free, open source software, tends to lag behind the commercial operating systems.

The most modern way is: you find a "Download" button on the web, click it, and everything happens automatically (but you must click OK in a few dialogs that open.) Most GIMP plugins don't work this way.

An older but still common way is: you download a 'package' or a 'installer.' Typically, the suffix of the file is .exe, .msi (microsoft installer) or .deb (Debian package.) After downloading, you must double-click on it. Then, as a program (a self-installer), it runs (or another program runs (called an installer that is associated with the file suffix)) , and unpacks its contents (another program or plugin) and puts the contents in the proper place (to be considered 'installed'.) Not all .exe files are self-installers, especially GIMP plugins (and not resynthesizer.exe.) It's rare for a GIMP plugin to be packaged this way.

The ancient but most common way for GIMP plugins is: you download an archive ((a .zip or a .tar.gz) when the plugin has many parts) or a single file (.exe or .scm or .py) that comprises the entire plugin.) Then you unzip and copy the file(s) to the correct place(s) (to be considered installed in GIMP.)

Much confusion reigns because there are so many uses of .exe: you must understand which .exe's are self-installers and which are not. (Not anyone's fault, just a relic of progress.)

Confusion also reigns because single-file GIMP plugins with suffix .exe or .py must go to a different place than single-file plugins with suffix .scm. (A deficiency in GIMP?)

Scheme files are scripts, Python files and Executable files are plug-ins. That's why they go to different directories.

What someone could do is the following:

1. Write a GIMP plug-in that registers itself as a file handler for binary executables, Python and Scheme files
2. If such a file is opened in GIMP (dragging it onto a GIMP window would probably be a common way to do that), the plug-in can ask the user if this file is a GIMP add-on and should be installed
3. If the user happens to have write access to the global plug-in directories, it could offer to install them there

P.S. the "just click download and Ok, Ok, ..."is turning into one of the most frequently used attack vectors against Windows systems, so I'm not really sure if it should be described as the "most modern" way.

Subscribe to Comments for "GIMP Resynthesizer Plug-In"