Precompiled GIMP on macOS does not recognize plugins
This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
Precompiled GIMP on macOS does not recognize plugins | Radon Rosborough | 21 Mar 17:01 |
Precompiled GIMP on macOS does not recognize plugins | Partha Bagchi | 21 Mar 17:12 |
Precompiled GIMP on macOS does not recognize plugins | Radon Rosborough | 21 Mar 20:24 |
Precompiled GIMP on macOS does not recognize plugins | Ofnuts | 22 Mar 10:15 |
Precompiled GIMP on macOS does not recognize plugins | Radon Rosborough | 22 Mar 16:14 |
Precompiled GIMP on macOS does not recognize plugins | Ofnuts | 23 Mar 17:14 |
Precompiled GIMP on macOS does not recognize plugins | Radon Rosborough | 23 Mar 18:27 |
Precompiled GIMP on macOS does not recognize plugins | Ofnuts | 23 Mar 21:14 |
Precompiled GIMP on macOS does not recognize plugins
Hello all,
I am attempting to install the Resynthesizer plugin for GIMP on macOS 10.11.6.
I installed GIMP 2.8.22 using Homebrew Cask https://github.com/caskroom/homebrew-cask/blob/master/Casks/gimp.rb and downloaded the Resynthesizer plugin version 1.0 from http://registry.gimp.org/node/27986
According to Preferences > Folders, the following directories are used for plug-ins:
/Users/raxod502/Library/Application Support/GIMP/2.8/plug-ins /Applications/GIMP.app/Contents/Resources/lib/gimp/2.0/plug-ins
The contents of the former are:
Permissions Size User Date Modified Name .rw-r--r--@ 6.6k raxod502 13 Apr 2011 plugin-heal-selection.py .rw-r--r--@ 3.2k raxod502 13 Apr 2011 plugin-heal-transparency.py .rw-r--r--@ 17k raxod502 13 Apr 2011 plugin-map-style.py .rw-r--r--@ 7.7k raxod502 13 Apr 2011 plugin-render-texture.py .rw-r--r--@ 3.3k raxod502 13 Apr 2011 plugin-resynth-enlarge.py .rw-r--r--@ 3.6k raxod502 15 Apr 2011 plugin-resynth-fill-pattern.py .rw-r--r--@ 3.3k raxod502 13 Apr 2011 plugin-resynth-sharpen.py .rw-r--r--@ 6.0k raxod502 13 Apr 2011 plugin-uncrop.py .rwxr-xr-x@ 62k raxod502 15 Apr 2011 resynthesizer .rwxr-xr-x@ 53k raxod502 15 Apr 2011 resynthesizer-gui
On restarting GIMP, I believe there should be a menu entry Filter > Enhance > Heal selection (among others), but there is no such item. Furthermore, I get no results from Help > Plug-In Browser when searching for either "heal" or "resynthesizer".
Have I misunderstood how to install plugins? Is there some kind of compilation step? Any way I can debug the situation?
Best regards, Radon Rosborough
Precompiled GIMP on macOS does not recognize plugins
Or you could simply download McGimp 2.8 series from my site and it includes resynthesizer. Or not. :)
On Wed, Mar 21, 2018 at 1:01 PM, Radon Rosborough wrote:
Hello all,
I am attempting to install the Resynthesizer plugin for GIMP on macOS 10.11.6.
I installed GIMP 2.8.22 using Homebrew Cask https://github.com/caskroom/homebrew-cask/blob/master/Casks/gimp.rb and downloaded the Resynthesizer plugin version 1.0 from http://registry.gimp.org/node/27986
According to Preferences > Folders, the following directories are used for plug-ins:
/Users/raxod502/Library/Application Support/GIMP/2.8/plug-ins /Applications/GIMP.app/Contents/Resources/lib/gimp/2.0/plug-ins
The contents of the former are:
Permissions Size User Date Modified Name .rw-r--r--@ 6.6k raxod502 13 Apr 2011 plugin-heal-selection.py .rw-r--r--@ 3.2k raxod502 13 Apr 2011 plugin-heal-transparency.py .rw-r--r--@ 17k raxod502 13 Apr 2011 plugin-map-style.py .rw-r--r--@ 7.7k raxod502 13 Apr 2011 plugin-render-texture.py .rw-r--r--@ 3.3k raxod502 13 Apr 2011 plugin-resynth-enlarge.py .rw-r--r--@ 3.6k raxod502 15 Apr 2011 plugin-resynth-fill-pattern.py .rw-r--r--@ 3.3k raxod502 13 Apr 2011 plugin-resynth-sharpen.py .rw-r--r--@ 6.0k raxod502 13 Apr 2011 plugin-uncrop.py .rwxr-xr-x@ 62k raxod502 15 Apr 2011 resynthesizer .rwxr-xr-x@ 53k raxod502 15 Apr 2011 resynthesizer-gui
On restarting GIMP, I believe there should be a menu entry Filter > Enhance > Heal selection (among others), but there is no such item. Furthermore, I get no results from Help > Plug-In Browser when searching for either "heal" or "resynthesizer".
Have I misunderstood how to install plugins? Is there some kind of compilation step? Any way I can debug the situation?
Best regards, Radon Rosborough
_______________________________________________ gimp-user-list mailing list
List address: gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Precompiled GIMP on macOS does not recognize plugins
Or you could simply download McGimp 2.8 series from my site and it includes resynthesizer.
Yes, of course. I have done this in the past. However, it is not a general solution.
Precompiled GIMP on macOS does not recognize plugins
The Python files should be made executable (chmod +x ...)
On 03/21/18 18:01, Radon Rosborough wrote:
Hello all,
I am attempting to install the Resynthesizer plugin for GIMP on macOS 10.11.6.
I installed GIMP 2.8.22 using Homebrew Cask https://github.com/caskroom/homebrew-cask/blob/master/Casks/gimp.rb and downloaded the Resynthesizer plugin version 1.0 from http://registry.gimp.org/node/27986
According to Preferences > Folders, the following directories are used for plug-ins:
/Users/raxod502/Library/Application Support/GIMP/2.8/plug-ins /Applications/GIMP.app/Contents/Resources/lib/gimp/2.0/plug-ins
The contents of the former are:
Permissions Size User Date Modified Name .rw-r--r--@ 6.6k raxod502 13 Apr 2011 plugin-heal-selection.py .rw-r--r--@ 3.2k raxod502 13 Apr 2011 plugin-heal-transparency.py .rw-r--r--@ 17k raxod502 13 Apr 2011 plugin-map-style.py .rw-r--r--@ 7.7k raxod502 13 Apr 2011 plugin-render-texture.py .rw-r--r--@ 3.3k raxod502 13 Apr 2011 plugin-resynth-enlarge.py .rw-r--r--@ 3.6k raxod502 15 Apr 2011 plugin-resynth-fill-pattern.py .rw-r--r--@ 3.3k raxod502 13 Apr 2011 plugin-resynth-sharpen.py .rw-r--r--@ 6.0k raxod502 13 Apr 2011 plugin-uncrop.py .rwxr-xr-x@ 62k raxod502 15 Apr 2011 resynthesizer .rwxr-xr-x@ 53k raxod502 15 Apr 2011 resynthesizer-gui
On restarting GIMP, I believe there should be a menu entry Filter > Enhance > Heal selection (among others), but there is no such item. Furthermore, I get no results from Help > Plug-In Browser when searching for either "heal" or "resynthesizer".
Have I misunderstood how to install plugins? Is there some kind of compilation step? Any way I can debug the situation?
Best regards, Radon Rosborough
_______________________________________________ gimp-user-list mailing list
List address: gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Precompiled GIMP on macOS does not recognize plugins
The Python files should be made executable (chmod +x ...)
Thanks! That fixed the problem entirely. Perhaps it should be added to the documentation. Or maybe this is too rare of a problem for that. (Although probably not, given that Resynthesizer has this error in its packaging.)
In any case, I told the Resynthesizer maintainers about it: https://github.com/bootchk/resynthesizer/issues/48
Thanks, Radon
Precompiled GIMP on macOS does not recognize plugins
Files in plugins are standalone programs. As such, in OSX as in all Unixen, they should have the executable bit.
Of course, some packaging formats preserve the flags so you don't have to worry about them, while others remove it (direct download of the .PY file).
On 03/22/18 17:14, Radon Rosborough wrote:
The Python files should be made executable (chmod +x ...)
Thanks! That fixed the problem entirely. Perhaps it should be added to the documentation. Or maybe this is too rare of a problem for that. (Although probably not, given that Resynthesizer has this error in its packaging.)
In any case, I told the Resynthesizer maintainers about it: https://github.com/bootchk/resynthesizer/issues/48
Thanks, Radon
Precompiled GIMP on macOS does not recognize plugins
Files in plugins are standalone programs. As such, in OSX as in all Unixen, they should have the executable bit.
Perhaps this is a misunderstanding of the plug-in format on my part, but why would the Python scripts be executed as standalone programs? Wouldn't they be imported by the main GIMP runtime? I can't imagine how the register() function call would work otherwise. Plus, the documentation at
https://www.gimp.org/docs/python/index.html
says
In fact, you will find that the GIMP-Python scripts start with the line !/usr/bin/python . The GIMP extension is loaded with the familiar import command.
From the Resynthesizer issue I linked:
A better fix [than making the scripts executable] might be for someone to fix GIMP itself. This is a long-standing gotcha, as you probably found on the mailing list: many people know the issue exists and how to solve it. AFAIK, no other app requires python scripts to have executable permissions. I could be wrong, maybe there is a valid reason GIMP requires it.
Precompiled GIMP on macOS does not recognize plugins
On 03/23/18 19:27, Radon Rosborough wrote:
Files in plugins are standalone programs. As such, in OSX as in all Unixen, they should have the executable bit.
Perhaps this is a misunderstanding of the plug-in format on my part, but why would the Python scripts be executed as standalone programs? Wouldn't they be imported by the main GIMP runtime? I can't imagine how the register() function call would work otherwise. Plus, the documentation at
https://www.gimp.org/docs/python/index.html
says
In fact, you will find that the GIMP-Python scripts start with the line !/usr/bin/python . The GIMP extension is loaded with the familiar import command.
From the Resynthesizer issue I linked:
A better fix [than making the scripts executable] might be for someone to fix GIMP itself. This is a long-standing gotcha, as you probably found on the mailing list: many people know the issue exists and how to solve it. AFAIK, no other app requires python scripts to have executable permissions. I could be wrong, maybe there is a valid reason GIMP requires it.
Gimp (at least on Unix) doesn't really care what the executables are. Things in the "scripts" subdirectory are scripts and are really loaded by the Gimp script-fu executor, but in "plug-ins" you can have anything that Unix will execute (and at registration time, Gimp will execute them blindly...) . and the binaries have to be marked executable as well, it is not specific to Python...