![]() AFAIK, /usr/local/lib/gimp/2.0/plug-ins is unique to a plugin built and installed using automake tools on an Ubuntu platform. ![]() It doesn’t matter what the exact location is, if a user adds a path to the preference, GIMP should look there. But I haven’t yet found any official documentation about this change in GIMP. ![]() That path name “…/gimp/2.0/…” makes more sense than the old path …/gimp2.x/…" since most plugins are mostly dependent only on libgimp2.0 and not any specific features of any GIMP version e.g. Maybe that is the intended location of third party plugins, and that anyone that uses flatpak will have that directory and that Ubuntu will start supporting flatpak by creating that directory. There is no /app directory on my machine. When I installed GIMP 2.10 one of the paths is to the sandbox (/home/foo/.var/…) and the other was to /app/lib/gimp/2.0/plugins. I don’t understand why any of the older “usual” paths for third-party plug-ins is not one of the default plugin paths in GIMP (in Edit>Preferences>Folders>Plugins). And maybe that will change after Ubuntu starts distributing 2.10.ĪFAIK, before 2.10, the usual place to install third-party plugins was ~/.gimp2.x/plug-ins, not ~/.config/… Because I think that path was one of the default plugin paths in GIMP. Yes, it is non ordinary, but Ubuntu sometimes does things a little out of the ordinary. Seem to recall a similar post a week or so ago.ĪFAIK, /usr/local/lib/gimp/2.0/plug-ins is unique to a plugin built and installed using automake tools on an Ubuntu platform. Screenshot - resynthesizer / heal-selection: Resynthesizer / nufraw / gmic-gtk for example but many of the old Gimp 2.8 plugins work. Some of them I do compile in a 'buntu 16.04 VM. So at the moment my plug-ins look like this, and all of them work. Other compiled plugins might/will have dependencies which because of the flatpak ‘sandboxing’ need to be added. Resynthesizer will work without problems. What I did add was a more convenient place for resources, scripts, brushes, plug-ins as shown.Ĭompiled plugins are another matter. The more regular profile /home/rich/.config/GIMP/2.10/plug-ins/ is there, but I can not remember if I had to add to the Edit → Preferences → Folders → Plug-ins section. The flatpak profile /home/rich/.var/app//config/GIMP/2.10/ was created (originally with gimp 2.10.0) but was empty, why I do not know. Sorry to have to refer to screenshots and your installation might have installed differently but… ![]() You can certainly add plugins to the flatpak - this using Kubuntu 16.04 and Gimp 2.10.2 do I need a new libgimp2.0 as well as changing the scripts to define a new install location? But shouldn’t my changes to the preferences mean 2.10 would find the plugins for earlier versions of GIMP? Maybe I made a silly mistake.Īlso, anyone have notes on building plugins for 2.10 using the old automake scripts for the gimp plugin template, e.g. ![]() I suspect the build scripts need to be updated to the new install locations for GIMP plugins. I also built resynthesizer from source and installed it. Anyway, in GIMP 2.10, I changed Edit>Preferences>Folders>Plugins and added paths to the old locations (something like /usr/local/lib/gimp/2.0/plug-ins, which is unique to Ubuntu?) and restarted GIMP, but it still did not seem to find the plugins I expected (specifically, resynthesizer set of. I did not see that documented in the GIMP 2.10 release notes. I saw that the location of plugins has changed in 2.10 (to something like ~/.var/app…). It seems like it does not in my case: Ubuntu 17.10, I installed GIMP 2.10 from the official flatpak install, and installed the distribution package gimp-plugin-registry. Does GIMP 2.10 find third-party plugins installed for 2.8? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |