On Tuesday 17 July 2007, [EMAIL PROTECTED] wrote: From: Hendrik Sattler <[EMAIL PROTECTED]> > Zitat von Axel Roebel <[EMAIL PROTECTED]>: > > So in short: if you intend to be portable with the current > > and the upcoming version of cmake > > better don't use VERSION and don't use EXCLUDE_FROM_ALL. > > So what? Xcode and Cygwin Makefiles generators are broken, that's no > reason for me to not use the stuff that works with all others. > On MacOS X, you can probably use plain Makefiles instead?
Very wise, as long as you use the project yourself you can do that. If you publish your project and you get users complaining about not being able to use what you provided you'll see that it will be you who has to deal with the problems. >Not using VERSION property is not a good choice. Some systems that do >not know about SONAME (which ones?) may need it to be able to >use/install multiple versions of a library at the same time. You got the point. So that's why I considered VERSION to be important to be fixed. >PS: if it's not a generator that's broken, then it may as well be the >make implementation or a strange concept of an IDE. And if that all >works, you'll always hit messy compilers ;) Very helpful this remark as well, thanks a lot. So you suggest not fixing cmake bugs because if they are fixed maybe the makefile or IDE will be broken anyway. Did you think about the main reason cmake came to existence? At least as I understand it and why I use it and what is written on the main cmake page is: platform and compiler portable project generation. The attitude my build tool is important but yours is a mess is certainly what is the least helpful here. -- Axel Roebel IRCAM Analysis/Synthesis Team Phone: ++33-1-4478 4845 | Fax: ++33-1-4478 1540 _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
