Script/Plug-in a 32 or 64 bit?

[Ofnuts]

(07-01-2019, 07:41 AM)rich2005 Wrote: A Gimp scripted plugin (ie a text file) either script-fu (.scm) or python (.py) is Windows agnostic. It will run in either a 32 bit or 64 bit installation. More important is the version of Gimp. A script written for Gimp 2.6, for example the old FXfoundry scripts are unlikely to work correctly. Of course some of those have been updated over the years but many have not. Python plugins, as well as affected by version of Gimp, can also depend on the version of python included with Windows-Gimp, for example the non-working arakne path plugins. Even those can sometimes be fixed for Gimp 2.10.x

Compiled plugins something.exe are a bit different. They can come in either 32 bit or 64 bit versions but mostly 32 bit for maximum compatibility.

A 32 bit plugin will work in a 64 bit Windows but the reverse is not true. A 64 bit .exe does not work in a 32 bit Windows.

How can you tell the different Windows 'flavour'? Apart from diving into the Windows control panel Use the file manager, if there are both C:\Program Files\  and a C:\Program Files (x86) folders then the Windows is 64 bit . Just a C:\Program Files and Windows is 32 bit.

Then of course the previous also applies. A compiled plugin for Gimp 2.6 is unlikely to work with Gimp 2.10 and difficult for the ordinary user to fix. How can you tell 32/64 bit in Windows. Not so easy with the tools MS provides. See previous post.

EDIT: Of course this does not really help with moving from Win 32 bit / old Gimp to Win 64 bit new Gimp. It is just try-and-see Sometimes you can see a problem by running Gimp with the --verbose switch. Not often correctable with Windows.

To muddy up the waters a little bit. In a 64-it Windows you can run a 32-bit Gimp. Now you have to wonder if the "bitness" of the plugins is important, in other words, can you use a 32-bit plugin with 64-bit Gimp and vice-versa?