I was recently playing little bit with cmake and it can generate "portable" IDE projects (that is independent on cmake itself) as long as you set for the generation the directories relative to the build directory and you do not make checking of external library directories. I am not sure about other IDEs but for Microsoft compilers it is OK because there is no "configure script" (or anything of equivalent functionality) for FLTK project and the standard library directories are inherited from whatever is set within the IDE itself. That means cmake can indeed generate portable Microsoft projects without dependency on external tools (like cmake itself) and can be used for the generation of MS project files before producing the distribution tarball.
R. Fabien Costantini wrote: >> Presently we have 3 different targets only for ms visual development > plus 2 borlands and one watcom build env. >> We could forbid the maintainers to directly modify these build files, >> but the build files could be still generated by cmake and included in the >> source tree > This could be hard feasible for 2 reasons : 1) cmake adds internal cmake > tools check instrumentation in the build files, 2) cmake is not proposing as > is, other choices than writing its build files at the root. > > Finally, it is not obvious that it would not be justified to require from the > user to use cmake for all win32 (non cygwin) targets when considering the > numbers of targets matches : about 8 targets excluding the unix makefiles > targets. > > _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
