GIMP Version: 2.8.4
Operating System: Windows
OS Version: Win 7 - 32 bits
GIMP Experience: Beginner Level

List any relevant plug-ins or scripts:
all plug-ins in C

---

Hi Rod,

if you are still playing somehow with the environment to compile Gimp plug-ins in C provided nicely to us by Samj, I like to tell you about my progress.
I started recompiling the plug-ins provided to us by Samj in those mythical folders like "gimp-nameofplugin_32bits-64bits_gimp-2.8-Win".
For the moment I ignored those that look too complicated to me and considered only those which have a simple c source.
The reason for recompiling is my desire to change the menu (which was at the origin of the request made to Samj).
Some of them did compile without problems.
Some of them did not compile due to the following line of code:
"bindtextdomain (GETTEXT PACKAGE, LOCALEDIR)"
Initially I was tempted to consider the GETTEXT being the problem, but it was not so, the problem is LOCALEDIR which is not solved automatically by the environment; so my solution has been to add a line at the beginning of those plug-ins: #define LOCALEDIR "/locale", and they got compiled; it's maybe not an elegant solution, probably there is a correct solution in enhancing somehow the environment in order to get the reference solved automatically, but it works.
Then I tried to recompile the "max-rgb.c" (a plug-in in which I'm interested, you probably remember it was the one on which I stopped at the end of the post @samj).
In there, the problem lies on a line of code which says "gtk_box_new ...".
For a long while I tried to understand, until I found that this statement is valid only with GTK 3.0, while our environment is GTK 2.0; I tried to include GTK 3.0 in the environment, but unsuccessfully; eventually, I got the solution by googling (another c plug-in - beautify.c - was changed for the same reason): we must insert the following lines of code:
/* compatible with gtk2 ---- aggiunte inizio ----- */
#if GTK_MAJOR_VERSION < 3
GtkWidget *
gtk_box_new (GtkOrientation orientation,
gint spacing)
{
if (orientation == GTK_ORIENTATION_HORIZONTAL)
return gtk_hbox_new (FALSE, spacing);
else
return gtk_vbox_new (FALSE, spacing);
}
#endif
/* compatible with gtk2 ---- aggiunte fine ----- */
I post these info here in case you (or someone else who installed the environment to play with) are willing to continue on the road...

Good tips, thanks.

Something you should remember when compiling with this a fore mentioned WINDOWS environment.It is set up to compile plugins for Gimp-2.7 so some plugins will be very hard to compile for Gimp-2.8 builds. If you want to compile WINDOWS c plug-in src files correctly you will need to update the Gimp version by recompiling BABL, GEGL, and Gimp-2.8 src files.
Undoubtedly you will also have to re compile GLIB and most other LIBRARY DEPENDENCIES first. I am almost sure of it.
Just thought i would mention that. Some plugins will compile if they do not need certain libraries to do so, others will error on OR .

You could try just updating the compiler (GCC) or the LIBS that the GIMP plug-ins need to run.
eg GLIB, INTOOL, LIBTOOL, PKG_CONFIG, PANGO, CAIRO ect..ect. Instead of recompiling GIMP again. This may or may not work. I have never tried this method. Be sure to compile or replace both lib and lib-dev for these dependencies if you do.

@Graechan
thanks, that is one of your first suggestions I followed when I was just a "novice" in gimp-chat.
The problem on my home computer is that from time to time I have to delete pluginrc to get it recreated (a problem about date last plug-in update which does not function correctly in my env, I don't know why), so it's a bit frustrating to re-change everytime the menu.
Anyhow, thanks to recall it to me.

@Rod
I appreciate your recommendation to update my Gimp compiling environment, but I'm not capable as you are, so I wait until another "gift" will allow me to create a new compiling environment.
By the way, I take this occasion to express a doubt I have: I know there is one link by which you can get any day a new up-to-date compiled version of Gimp (32 bits only, but that what matters to me); so, why that people does not insert also a link to their environment (the one they use to compile) so who is interested could re-create it in his own computer? It would be very much appreciated (I don't think the compiling env will change continuously, so once linked it may stay there for a long time, probably...)

@Dinasset
Environment: Take a look at this >> viewtopic.php?f=23&t=8111

Personally i prefer an sh file to always having to find dependencies.
Then you need only have that one file, and run it in Minimal System. The file would download everything you need and systematically compile everything in the correct order. One script to run and that's that.

There used to be one. I may still have it lurking about on Media Fire. I will check. Of course it is for older dependencies (BABL, GEGL, and GIMP), but it can be edited to work i am sure.

The sh file is sort of like a GIT command (sort-of).
It auto links to the FTP GTK site for win32 libs, downloads and if necessary compiles them and installs them to the correct directory. Then it links to GTK+ and GLIB files and does the same thing. Compiles and installs them.
Once the first step of downloading and updating each lib dependency is finished, BABL is downloaded compiled and installed.
Then GEGL, and finally GIMP.

Pretty simple really.

Thanks Samj, thanks Rod!
I will have a look at what Samj indicates (theoretical, for now, I'm not at home), I hope the level of info there is at my (low) level of (in)competence.
I also wait upon what Rod anticipated (even if I don't know - in my ignorance - what an sh file is); I hope it will be really easy for me (and other interested people) to follow the necessary steps
Thanks a lot

@samj
just started reading referenced info.
One simple question to understand the flow (probably a silly question for less ignorant people around here):
- one win (32 bits) user like me, using those info, will as first step install a virtual Debian machine under windows? then perform all the rest of the steps under this Debian machine?
Thanks

@Dinasset

With a 32-bit machine you have to use a 32-bit virtual machine, for example :
http://www.aljacom.com/~gmic/GimpEVAL-2 ... -32bits.7z
Volume : (1 658 776 406 octets) / MD5 : 8aec87f1b17a8c805f9c26274a63063b

To see what happens I will suggest using scripts from July 31 in the archive:
http://aljacom.com/~gmic/divers_compilation_croisee.zip (10 320 409 octets) / MD5 34478d03d735bf520e45e14712750449 / version 20130803

Use this command to compile the stable version : MODULE=gimp-stable ./build

You can analyze the scripts, they give the compiler options, patches, etc.. They can inspire you to create your script as you suggest Rod.

The results of compilation can be used to create your environment.

Agreed. The script could simply duplicate the environment you provided to us Sam. Thereby updating all the libraries to an up to date status.
The trick is to find all the dependencies, be sure the links are always reliable, and adjust the script accordingly to mimic the present compile environment. You could do this for both 32 and 64 bit systems.
Great idea Sam. I will check out the scripts you provided.

Thanks again for all your contributions, and help to me. It is much appreciated.

Having reliable links to GIMPS dependencies is half the work.

Rod (Allow at least 1 gigabytes of memory for the virtual machine if you use it).

Scripts are created by Drawoc : https://github.com/drawoc/windows-gimp-jhbuild
I thank him for his excellent work

Thanks!
Sam can you confirm these as the newest dev packages for building GIMP-2.8 version?


I am updating the old SH file i used before.
Going to attempt that first i think.

Also i need to know if the install path is /env or /mingw for all dependencies?
My fstab points to


So i am assuming /mingw is correct?

@Rod

You can see all the versions by editing the files .pc which are located in /lib/pkgconfig
for example in the archive http://aljacom.com/~gmic/gimp-2.8.7-201 ... ortable.7z , cairo.pc >> Version: 1.12.14

For the environment :
You need to edit these files for prefix=/foo match reality.
Place all the files .pc in a directory recognized by pkgconfig.

I do not think the old environment for Windows 32bit will work (compiler).


I suggest you use this compiler (Windows) :

http://sourceforge.net/projects/mingw-w ... g%20Win32/


http://sourceforge.net/projects/mingw-w ... %20Builds/
or
http://sourceforge.net/projects/mingw-w ... p/download


Mingw :
http://sourceforge.net/projects/mingw-w ... mingw-w64/

Libraries :
Edit 20130806 for 32 bit
http://download.opensuse.org/repositori ... .2/noarch/

64 bit :
http://download.opensuse.org/repositories/windows:/mingw:/win64/openSUSE_12.2/noarch/
(do not forget to edit .pc files)

Actually the script seems to be running fine except i cannot configure the local host for the needed libs.
Here is my error.


The url seems to be correct.

GOT IT! - had to change the local host url to

If this works and it seems to be so far, i will attach the SH file here after.

@Rod

I do not know if it helps, here is some information on scripts by Drawoc :
Links to libraries are in the files ".moduleset".
The compiler options are in "build.jhbuildrc".
Patches are in the folder "/patches".

I'm sorry if I do not understand all the questions in English...

Good luck building your development environment

Thanks Sam. I will look at those tonight.
The script is working as far as finding all needed dependencies online downloading with WGET, and installing/unzipping them correctly into mingw directory using the UNZIP utility.
A few still need to be compiled by doing them manualy.Some have a slash that i can't seem to find that causes a double slash to be added to the download link of some dependencies. GTK RUNTIMES is one of those.

I have to update to a newer version of GLIB so GEGL will compile. Forgot how much fun this all was.
Right at this time i am having trouble linking GLIB to FFI. Any ideas?
I tried adding the LIB and CFLAGS to the profile, and the fstab file but no luck yet.
For some reason libffi installs into mingw/lib/libffi/include , instead of mingw/include. At any rate GLIB can't link to the libffi h files.

Just a few bugs to work out. Nothing new hey!

Bonjour,

I wrote a small manual in French to update the build environment I propose to download.
http://www.aljacom.com/~gmic/mise_a_jou ... w-gimp.txt

My desire was to compile gimp-plugin-template in Windows with newer compilers : gcc Version 4.7.3 (rubenvb-4.7.4-release)
The result is a minimal environment, there will be corrections and additions (compilations, libraries) to be done by the users.