I've got the whole kaboodle compiling now under VS NET with gmake; the libs, fluid, test programs.
Also have a small 'fltk configration' screen (via 'gmake configure') which prompts for debug/release and verbose/silent build options interactively, or can be overridden by supplying NAME=<value> on the gmake command line. I moved all the Makefiles files into a subdir (buildtools.windows), and there's only a gmake.bat added to the top level directory which, if invoked, will run the configure screen, and install the gmake oriented Makefiles into the source dirs. This, I think, addresses some of Fabien's concerns about too many files being in the source dirs. My technique is to keep the files hidden, and only populate them into the source dirs if gmake.bat is invoked. Also, a 'gmake distclean' would get rid of them all. Will upload a new tarfile within the next day or so, time permitting. The current tar file extracts as follows: gmake.bat buildtools.windows/gmake.exe buildtools.windows/unconfigure.bat buildtools.windows/configure.bat buildtools.windows/Makefiles/fluid/ buildtools.windows/Makefiles/fluid/Makefile.MICROSOFT buildtools.windows/Makefiles/jpeg/Makefile.MICROSOFT buildtools.windows/Makefiles/png/Makefile.MICROSOFT buildtools.windows/Makefiles/src/Makefile.MICROSOFT buildtools.windows/Makefiles/src/gmake-fltk-include buildtools.windows/Makefiles/src/gmake.bat buildtools.windows/Makefiles/test/Makefile.MICROSOFT buildtools.windows/Makefiles/zlib/Makefile.MICROSOFT buildtools.windows/Makefiles/Makefile.MICROSOFT buildtools.windows/Makefiles/gmake-vsnet-include Only the gmake.bat would live in the top level dir, and has the small bit of logic to run the configure.bat script which puts the gmake files into place, and the 'gmake distclean' which uses unconfigure.bat to remove them again. There are several files, but they are small and easy to read, and allow unit testing, so that one can just eg. cd into the jpeg dir and type 'gmake' to build just that lib. Comments welcome.. _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
