Here are the port plugins so you can use GEGL graph non-destructively in 3.2



port gegl graph and port color and port crop and the rest like port gradients that are lousy but still usable. Also I think I made port oilify so people can use oilify non-destructive.

Can someone confirm if these plugins also work on 2.10 or before 3.0.6 ?

https://mega.nz/file/gDsBWYSb#TTH6u5xcK ... KlTIqWGROs




Here is the compile environment for Windows, its 64 megabytes when zipped, 185 mb when unzipped.
and around 700mb or more when all dlls are compiled. This is massive and if anything is moved around it won't compile successful. IT NEEDS gettext-windows


Please compile using Mysys2 with windows_master_build.sh in each major folder or in each individual folders build_plugin_windows.sh for a single plugin or group of plugins that go together like GEGL Effects.


The major folders cannot be all compiled together, so each one will have to be done one at a time.

1. Final_Filters_here (140+ main non AI plugins)

2. AI_plugins (the AI plugins, AI hybrids and duplicates of natives they need)

3. port_plugins (the port plugins like GEGL graph non-destructive, oilify non-destructive, and color fill)

4. official (ignore this, its copies of GEGL official Styles, GEGL official Inner Glow and GEGL official Bevel that ship with GIMP 3)

GMIC and GMIC hybrids are not included because they were never available on Windows and need even more DLL's.



Let me know if you can reproduce my build environment. The verify_plugins.sh is the script DeepSeek made to verify it is not dependending on LibInt8 dll. It auto generates



Please someone test if you can compile and use these natively on GIMP 3.2.


Also offtopic, InnerGlow got a tiny update where the new mode doesn't accidentally hide the opacity slider.

Hi Contrast

A small problem to solve.
Your plugins are split into two large packages (all and AI).
There are 10 duplicate plugins in these packages (I understand the reason and you inform about it):
'gegl_op_thresholdalpha2'.
'gegl_op_ssg'.
'gegl_op_smoothedge'.
'gegl_op_outlinedeluxe'.
'gegl_op_metal'.
'gegl_op_loadport'.
'gegl_op_layershadow'.
'gegl_op_glassovertext'.
'gegl_op_geglchrome'.
'gegl_op_cbevel'
However, if a user mixes files from different builds, GIMP can crash.
ai/lb filters are yours (even if some are AI-assisted), so I think they should be shared in one package.

I compiled all Your plugins in msys64/clang64 (all 209 files in one package takes up 5 MB after compression).
I know it's GPL, but only with your approval can I share it here (because it will confuse users even more).

I am also confused. I need all plugins in one or 2 zip.

They were all compiled with GEGL 0.48

You are free to share my plugins without my permission and their binaries. You just have to link the source code here
https://github.com/LinuxBeaver/LinuxBeaver/releases/

Post I am making is NOT about my own Inner Glow filter, it is about someone else's. The filters name is gegl:psd-inner-glow by Warris and it isn't released yet and is still a maybe in the fate of GIMP team to decide if it releases.
https://gitlab.gnome.org/WarisMaqbool/g ... ner-glow.c

A two private plugins I made which are not on Github but still circulate here are literally just gegl:opacity, and gegl:oilify exposed to the UI non-destructively without any changes. because they are circulating GIMP Chat originating from this thread I posted about them here. They can cause issues with Waris's psd inner glow. Port Opacity (port:opacity) and Port Oilify (port:oilify) conflict with one another due to sharing the same plugin op name by accident and for some reason I don't understand they mess up his plugin.

I fixed it here. If you have oilify-port.so/dll and opacity-port.so/dll in your GEGL plugins folder you are at risk of this potential future crash, if not you have nothing to worry about and can ignore this.