> Christian Convey wrote: > > Yup, the autoconf/configure/make technique does seem to work. Someone > > really should maintain those CMake files... ;) > > I'm curious; what are the benefits for you building > fltk with cmake vs. make? > > I'm assuming you can still use cmake to build your own apps > against FLTK, whether FLTK itself was built with it or not..? > > I know the devs would like to keep the number of supported > platform/build environments as small as possible, with the > preference being the 'native' build system for each platform.
A few. I think most people find it far easier to develop CMake files than to develop autoconf files. Probably more importantly, CMake can produce Makefiles that work on Linux/Unix, Mac OS X, and Windows. It can also produce VisualStudio project files, Xcode project files, and KDevelop 3 project files, in case you want to work in those environments. And it can produce any/all of those using a single set of CMake files. I've used autoconf on one project's build system, and since using CMake, I can't imagine ever going back. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
