Building Gimp 2.0 on Windows XP?
Anonymouse asks: "Has anyone out there just had the urge to build Gimp 2.0 on Windows instead of using an installer made by a third party, hosted on a free web hosting service? It's probably fine but it makes me nervous, so I figure I should try building it on Windows instead...besides, it could be educational! Does anyone have any instructions/suggestions for building the source on Windows XP using MinGW and MinSYS? Keep in mind I have no experience with *nix, and my meek programing skillz only apply to Perl. Thanks!"
If you really want to compile from scratch, do it on Linux first with native Linux programs. When you get the hang of that, move to Windows. I'm all for sink-or-swim type trials, but, in this case, I think you'll sink. Very quickly.
Second that. Most software builds are much more extensively tested and used (and made easier and more reliable to build) under Linux. Linux distros come with a good set-up-in-a-standard-manner development toolset.
A lot of Windows port work isn't kept up-to-date.
Putting together your own cygwin or mingw toolchain (not that that's a bad idea in general) already is a severe pain in the ass. It can be real black magic to figure out what people last did to get primarily-used-on-UNIX-software building. When you couple that with the fact that there are all *sorts* of interesting problems that come up on Windows (case sensitivity suddenly existing, line feeds mattering, etc) things can get much more interesting.
May we never see th
Doesn't this belong on an appropriate mailing list or something?
11*43+456^2
That should be "case insensitivity".
May we never see th
And why don't you just go to the GIMP homepage, subscribe to the GIMP mailing list and ask the developers ?
... all in the correct order and with the right options (like Xft support, and if you want to use your graphic tablet you need XInput... at least on Linux/UNIX, YMMV on Windows of course)).
Seriously, if you're so lazy that you're using Ask Slashdot instead of their mailing list you should stick with the installer ! Especially since compiling GIMP 2.0 is diving into dependency hell (you'll need to compile about half a dozen libraries first, ATK, glib, GTK+,
Really? I don't know about other people, but where I work we do this stuff with computers!
Maintaining a team of people to autobuild would be really expensive, but maintaining a couple of computers to do it has mostly involved some setup costs.
And it has been utterly fantastic, in terms of making sure we don't deliver broken software :-)