This is why i didn't let the script dl the BABL, GEGL, and Gimp files for me or compile them.
Hence the dl links for them i gave you.
I only use the script to get the dependencies Gimp needs to compile correctly.Because they are w32 binaries and play nicely with MinGW.

Then i compiled
BABL-0.1.2
GEGL-0.1.2
Now i just need to figure out this GLIB problem *sigh*

I find it interesting you set the script to dl and compile 2.6.11
Why not compile 2.7.2? - if you set that version in the script and move the RAR to the tmp-packages folder the script should see it there (Allready There), and just untar and build it.(same with GEGL-0.1.2 and BABL-0.1.2
That was the whole reason i tried to compile it in the first place was to check out the new Cage Transform plug-in in the 2.7.2 version.

The reason I chose 2.6.11 is that I wanted to fiddle with the script using a version of Gimp that I knew worked under Windows. I figured getting the Perl part working would be challenge enough for me to start with. Then once I got Perl working, I could turn around and do the same thing with 2.7.2.

Oh i see good point.

Rod,
Just so you don't think I stopped, I thought I'd give you a bit of an update. I finally found out how to make the cross-compile work in Linux, now I just need to (really) understand how compiler and linker directives and flags work. There's still a bit of a disconnect in my mind that I'm working on. The fallout of this is that I broke my Linux Gimp installation and had to fix it.

Don't know if you noticed, but there are new development versions (0.1.3) of BABL and GEGL in the git repository; they haven't been made available as tarballs yet. On a related note, I wondered if you went through the compilegimp.sh script and updated all of the various source package versions. Nearly all of them have new releases since the script was last updated. Be aware when/if you do this to note that some of the dependencies names have subtle changes - most have hyphens replaced by underscores, and I think all now have the "_win32" after the version numbers. It took me an hour or so to track down all the changes.

I also found out that the script doesn't work in the Linux terminal if you type sh compile-gimp.sh. Doing it in this fashion invokes the wrong shell, and some of the commands inside the script fail. This probably won't affect the compiling on a Windows host through MinGW/MSYS as I think they use a bash shell already, which looks to be the type of shell the script was written for. Also (in my opinion), the script is way too complicated. I think 60% of the script is variables for parts of package names!

My $.02

Bob if you look earlier in this thread i mentioned i have GEGL and BABL -0.1.3 =)
If you want them PM me for the links.
Also when i run the sh script i just run it for the updated dependencies...not to compile everything.
Now i have all those dependencies so i no longer need the sh script.

You say you got Gimp cross-compiled on Linux?
Any chance you can cross compile Gimp-2.7.2 on Linux, and send me a link to dl it?
If you need the source i have it.

On a side note i heard GEGL may be coming out in a windows version.
If i could get this GLIB issue working.
I may just un-install msys and go back to cygwin.
I got the closest to compile with that.

Glad you are still going at it! Good luck Bob.
Keep me updated please.

If you want those links to Gimp, GEGL, and BABL PM me.

No, sorry, that wasn't what I meant. I installed the MinGW/MSYS full package under Linux, but I could not figure out how to make the cross-compiler work. That is what I got figured out. Sorry to get your hopes up prematurely.

I feel like I'm dancing around he edge of a solution, like when you are searching for a particular word but can't quite get it. When I do get it figured out I'll have a permanent dent in my forehead from smacking myself.

Yesterday was just an overall frustrating day, computer-wise. Besides having broken and repaired my Linux Gimp installation, my WinXP VM wouldn't start. I actually had to uninstall the VirtualBox software and fall back to a previous version. There's one piece of software that I need to run once a week that only runs under Windows... So getting through Saturday without opening a window and tossing my PC into a snowdrift was a challenge.

lol sorry to hear that Bob.
I am fine, i do not worry about Gimp getting compiled too much anymore.It's now like a far off dream of mine.To one day get on my windows command line and go OH MY! I see what i did wrong (which is probably how it will turn out).

OH MY! I see what i did wrong (which is exactly how it turned out)

I though i would just update this thread as i did manage to compile Gimp successfully for Windows.
Using Msys, and MinGW.

PM me for further instructions if you really want to cross that line of insanity.On the other hand you can tell everyone hey i compiled Gimp for Windows, which really is a big deal.Not many have.

More information here
http://www.partha.com