Well i wish you all the luck in the world Bob! =)
Along with my prayers and hopes .. heheh

If you do decide to compile with VB give me a holler, i have it installed too.
Didn't try it yet with Gimp.

Gimp is a strange one to compile on Windows.
I actually get a new error now with running gimp config file
It can not find the correct GLIB header files. =P

odd

I had another thought: since Gimp 2.6.11 (for example) has a Windows installer, and uses the BABL, GEGL etc, libraries, then wouldn't their .dll's exist on the system somewhere? If the linker could be pointed to them...

Rod,
Well, I partially followed your suggestions. I downloaded and installed the ActiveState Perl (however, did not restart the machine). I compiled and installed babl. The regular gimp compile script still couldn't find babl, so I copied the mentioned files:
libbabl-0.1-0.dll
libbabl-0.1.la
libbabl-0.1.dll.a
into the C:\MinGW\lib and C:\MinGW\bin , on the off-chance that they would be found in one of the two places. I also copied the babl.pc file into C:\MinGW\share\pkgconfig as directed. Then I decided to run the compilegimp.sh script you posted above. It still was hanging on the babl section, as previously discussed, so I took a chance and edited the compilegimp.sh file and commented out the first babl check [lines 568-580]. As you see, I left the "copying libbabl..." & "Ok7" lines intact so I could see the script skip the check. With this change the script downloaded, compiled and built, and installed babl again, and continued to the point where it checks for the particular perl version and then stopped. I hope that this is because I did not reboot after the ActivePerl install, so perhaps the new path isn't being picked up.

This seems to be sort of progress, and I think you solved this problem before in case the reboot doesn't work for me. I wanted to get this down before the reboot. There is something definitely wrong with this script; how can it pass the perl check (OK3) then fail it?

BTW, I was out of pie, so I was drinking coffee and eating chocolate-chip + walnut cookies. Even with the coffee I finally went to bed @ 2AM, so I discovered all that when I woke this morning.

Yup, fun ain't it? =)
Don't feel bad i didn't get much sleep either the first time i tried to compile it.
It's almost like it's addicting.
What it did probably,was run the sh okay, but then after it began running i am
assuming GEGL configure script it got the error?

It seems all the scripts (configure), are written differently to me.
They all seem to look for stuff in strange and different locations.
One will look for Perl in C:\usr\opt\Perl while another looks for it in C:\usr\bin\Perl
This is why i said to copy (not move), your Perl folder in C directory to the bin folder in MinGW.
Another thing you will certainly run into is that the Gimp configure script will look for GLIB and INTOOL and all kinds of things all over the place. C:\MinGW\bin and lib and C:\MinGW\Msys\bin and lib
It's all over the place.

You might want to try this
Place
C:\MinGW\bin;C:\MinGW\lib;C:\MinGW\include;C:\MinGW\msys\lib;C:\MinGW\msys\bin;C:\MinGW\msys\include
all in your Paths environment variable
Plus C:\Python26\bin;C:\Python26\lib;C:\Python26\include in your Python_Path environment variable
Maybe even add the Perl paths too.
I use C:\Perl\bin\ and C:\MinGW\bin\Perl in mine - it seems to find those

If you look at the configure script you can find all the variables it looks for and you can add them correctly to your environment variables.

You definitely will learn a lot compiling Gimp on a windows platform ..

Rod,
No, it's when Gimp's configure script begins to run; babl and gegl compiled okay, then during the gimp configure it looks for perl in bin/perl, then checks for the perl version. I haven't moved my perl yet, so that's next, plus trying a modified the path again per your last post. I'm also not sure that the compilegimp.sh is pulling the correct BABL and GEGL versions. I know BABL is at least 0.1.2, but I keep seeing references to babl-0.1.0.

I'm going to give my 'puter a break for a bit - it took almost 3.5 hours from start to get this far, the XP VM running wide-open. The cpu core temp was hovering around 150-160 degrees F, and it's been a while since I dusted....

lol - yes don't let Gimp kill your machine Bob.
Time for another cookie .. heheh

Hey can you paste out the new sh script for me to copy and try?

Rod,

Here's my version with the commented-out section which I outlined above. I also modded the script to fetch the current stable version of Gimp (2.6.11).

I tried adjusting the script to get the current stable version (0.1.2) of BABL and GEGL, but BABL breaks the script because it's own compile script tries to build a suite of test programs, and they fail to compile because of "pthreads"; this failure breaks the BABL compile script which in turn breaks the rest of compilegimp.sh (the GEGL has to be the same version as the BABL, AFAIK). Until I figure out what's going on there I have to work with previous versions of BABL and GEGL. (Did I repeat myself? ) Anyhow, I left the change to get the current stable Gimp, but reverted the change to get the newer BABL and GEGL.

I have not yet tried this, maybe in about 1/2 hour.

I want to finish watching an episode of an anime series I've been streaming. Since Mama went to bed the TV is free, so I'll start the script then go watch an episode of Stargate Atlantis and maybe some episodes of The Nanny...

LOL, sorry couldn't resist =

Everybody needs a hobby.

Rod,
Here's a couple more pieces of the puzzle.

I hacked at the actual compile script for Gimp, commenting out the portion of the test for perl. This would be the section which generates the line "checking for perl >= 5.8.1".

If you type "perl -v" into the MinGW shell, it returns "This is perl, v5.6.1 built for msys" etc.
If you type "perl -v" into a Windows command window, you get "This is perl 5, version 12, subversion 2" etc. (This is the current ActiveState Perl.) This means that MinGW is still finding its own version of perl, and likely not even trying to continue searching the path - which makes sense, as the PATH has MinGW as the first two entries as recommended by the MinGW manual.

Okay, the next thing is that the configure script conducts the following test:


This is a one-line perl program. The variable $INTLTOOL should expand to "perl"; the -e tells perl to execute the statement "use 5.8.1", with the output redirected to null. The use function in this context tells perl to act as if it is actually perl v5.8.1, presumably for backwards compatibility. The glitch occurs because of the PATH issue I described, combined with the fact that the MinGW perl is only 5.6.1...it cannot pretend to be a version higher than itself, only lower.

I'm going to try to change my path so that the ActiveState Perl is found before the MinGW version.

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