......I'll stand over here

I've had it with 2.9.1.
Too many bugs,memory leaks and gegl operations slooooow and some not working at all.
In general it appears slower than 2.8.
Color management disabled.

I'll try again in maybe a month or so.
Gerard.

I have posted a web page that describes (in very great detail) how to compile Gimp 2.9, using MinGW on 32-bit Windows. I noticed Partha's site some time ago, and decided that I would provide more detail, even for those who never heard of MinGW or compiling. This is in the hope that some newbies might want to try the program, which might help with bug reports.

The page has nothing about 64-bit. Can't help you there. My approach uses files from "Gimp Portable" latest version (now 2.8.2), most (not all) of which are over-written during compilation of 2.9. In particular, since Gimp Portable now includes Python, preconfigured to work with Gimp, it is possible to compile 2.9 with Python disabled. Then, at runtime, 2.9 finds the Python from Portable 2.8 and uses it. Also, I did not find it necessary to use external Perl.

The compiled 2.9 appears to be portable, probably because it is self-contained. I haven't looked at this in great detail, but if compiled using my method and file structure, I can copy out the necessary folder, and launch it via Windows command (rather than MinGW shell). My page describes this.

Note: Awhile back, there was a color management problem in 2.9, apparently due to a Gegl bug. That bug has been fixed. Currently, there is color management (needs testing, of course). Also, the program is not as slooow as it used to be. Needs improvement, but is better.

http://robertallgeyer.com/content/speci ... p-2.9.html

Many thanks Hah_Bumbug !
For a long time (to no avail) I was looking for the exact help.
I will try this weekend according to your instructions.
The effects and problems write here...

@Hah_Bumbug
Welcome !

you did a amazing work never seen a such detailed guide to compile gimp on Windows...i may even reinstall MinGW and give a try.

thank a lot !

I compiled 2.9.x from git 2 days ago but it froze trying to use gegl.
With Linux this is easily done once the necessary tools are installed.
I entered a bug report months ago,forgot what it was about,but got a very grumpy answer from Michael.
I'm not sure it's appreciated.
Gerard.

Thanks for the feedback, from those who visiting my site about compiling Gimp 2.9 on Windows 32.

In the last few months, there have been some critical changes in Gegl. Some of them are very recent. I believe that Babl also had a change, a few months ago. So, if you compiled before, but had a problem, try again (with new Babl and new Gegl, from GIT).

I have also compiled 2.9 on Ubuntu and openSUSE. If you do this, you will need Ubuntu 12.10 (current dev) not 12.04, or openSUSE 12.2 (not 12.1). And, the Babl and Gegl must come from recent GIT, not the distro packages.

But my web page will have nothing to say about Linux, since that is thoroughly discussed elsewhere.

Over the next few days, I may make a few changes to my web page, so that it is easier to read. I noticed that early visitors came from Poland, Finland, and Italy.

Hi Robert
Your recipe is a great
Do you know how to turn off the console window (GIMP output)?

PS.
One more question:



Yes, it works for me in a different location - but I can not delete file:
c:\MinGW\msys\1.0\local\lib\babl-0.1\cairo.dll - because then I have a problem error.
No path - be it only for me the problem ?

EDIT: My original reply here was incorrect.

Correct:

1. The console (command window) must always be active, when the development version of Gimp 2.9 runs. You can minimize it, if you wish. Some debugging messages will appear in the command window.

2. On my original web page, I described a second method for launching Gimp 2.9 by another method. I noted that it worked for me, but might not work for others. As the above post showed, it did not work there. In fact, I now know that the second method ONLY worked for me. So, forget about it. I have revised my web page. The problem had nothing to do with international locale.

Perhaps that is also the reason-I had to change (in point. 6 a):


on:


Most important, however, is that GIMP 2.9.1 can be run.
There is a lot I have to learn about compiling - and your great tutorial helped me a lot.
Thank you very much