I wrote a guide to getting nip built under windows. It is a big-ish GTK program, so most of this will apply to gimp as well: http://wiki.vips.ecs.soton.ac.uk/bin/view/Main/VipsMingw Though gimp wll be harder (it's much more complicated and it needs more stuff). After all that effort, you'll only have a half-arsed development environment :-( debugging will be painful and building will be slow. I'd only bother it if you really need to build a native win32 binary. On 12/11/05, Kevin Cozens <kcozens@xxxxxxxxxxxx> wrote: > Michael Schumacher wrote: > > Building GIMP isn't hard. Getting the build environment working is the > > harder part, and something you'll have to do for plug-in building as well. > > > > There's a section in the wiki covering this > > http://wiki.gimp.org/gimp/HowToCompileGimp/MicrosoftWindows > > In can be very difficult. It took me a while to be able to succeed in getting > a build environment for Windows. The problem is in locating and downloading > all the packages that are needed. The scripts that supposedly downloade > everything needed were out of date or incomplete. Unfortunately I didn't keep > accurate enough notes to determine the main stumbling blocks. If the mood > takes me, I may start from scratch again some time and carefully document my > steps in order to get a better guide to setting up a build environment for > Windows. _______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
