On 27.02.2010, at 00:24, Albrecht Schlosser wrote:
> However, I have doubts concerning CMake :-( because CMake is
> something that can change rapidly. It's more like autoconf/configure
> than a static IDE. Recently we had to add some tests to detect
> the new glibc headers (scandir), and there are lots of files
> that contain some programming code in "CMake language" (just
> like configure.in) or even c/c++ code for the tests.
...
> 
> Please don't understand me wrong. I don't want to say that the
> fluid approach is wrong, but we should probably concentrate on
> the file list part only for CMake. And maybe this part could be
> done, whether the rest of the CMake files is ready or not :-)

Yes, that is probably the best way. I was hoping that Fluid could one day 
generate the IDE for new FLTK-based projects that are not part of the FLTK 
library setup itself, so users can rapidly start a new project. But for now, an 
update of the source file lists and targets should be sufficient.

I really do not want to write another build system here that takes all possible 
Linux distros, build environments, and IDEs into account ;-)


- Matthias
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to