Carol Spears writes: > my first instinct is to tell you *not* to try to build anything for gimp > on windows. Actually, if a plug-in is reasonably portably written, building it on Windows isn't necessarily any more complicated than on Unix. To build and install a plug-in foobar: gimptool --install foobar.c This would run the command: gcc -mpentiumpro -O4 -Wall -fnative-struct -I<top>/include -I<top>/lib/gtk+/include -I<top>/include/glib-2.0 -I<top>/lib/glib-2.0/include -I<top>/include -o <home>/.gimp-1.2/plug-ins/foobar.exe foobar.c -L/target/lib-mwindows -L<top>/lib -lgimpui -lgimp -Wl,--export-dynamic -L<top>/lib -lgtk -lgdk -lgmodule-2.0 -lglib-2.0 -lintl -liconv or, if you use MSVC: set CC="cl -MD" set CFLAGS="" set LDFLAGS="" gimptool --msvc-syntax --install foobar.c This would run: cl -I<top>/include -I<top>/lib/gtk+/include -I<top>/include/glib-2.0 -I<top>/lib/glib-2.0/include -I<top>/include -Fe<home>/.gimp-1.2/plug-ins/foobar.exe foobar.c -link -subsystem:windows /libpath:<top>/lib gimpui.lib gimp.lib /libpath:<top>/lib gtk.lib gdk.lib gmodule-2.0.lib glib-2.0.lib intl.lib iconv.lib It is a bug in gimptool.exe as currently distributed that setting CC, CFLAGS and LDFLAGS as above is necessary. Gimptool should be able to figure out by itself that if the --msvc-syntax flag is given, it shouldn't try to use the configure-time CC, CFLAGS or LDFLAGS autoconf variables if those are intended for gcc and GNU ld. <top> above would be replaced by the top installation directory of GLib, GTK+ 1.3.0, GIMP etc, and <home> with your home directory. Like on Unix, this requires that you have installed the gimp, gtk+-1.3.0, glib-2.0 developer packages (containing for instance the gimptool program, and headers and import libraries), plus the libintl and iconv packages. (If the plug-in doesn't need libintl or libiconv, you can edit out those from the command line.) --tml
