[CMake] simple ctest

th.tom at gmx.de th.tom at gmx.de
Thu Nov 5 10:19:27 EST 2009


> This sounds a bit pessimistic. Looks more like you're being bitten by a
> tight deadline ;). 

Yes, I am .. and I am tired of over 2 months of fighting with CMake. I would love to show a stable and reliable system (as mentioned before it is arround 400 CMake files and a lot of packages under win/linux/solaris) and I think I will work for this all night long :-/. However I got fire from all sides: old make-guys want to keep their system with make.rules make.common etc. New guys want to change to Java, Hudson, Maven, Ant ...

> Usually setting up nightly builds and dashboards is not
> what your usual programmer does. This is more the work of someone (like
> you)
> that knows these specifics. For everyday tasks related to adding targets,
> tests, external dependencies, I think the existing documentation is quite
> good, although it can surely be improved in certain places. Sequences of
> common things that your group of programmers do on a daily basis and in a
> structured way can usually be encapsulated in macros and functions, so
> their
> life becomes easier and less error-prone (many projects have their own set
> of specific cmake macros/functions tailored to their needs). If you do not
> want to expose certain 'inner behaviors', consider this as an alternative.
I've been working with these things and got good results! 

> Just to feed my curiosity, what is the existing alternative you're
> measuring
> cmake against?
The actual process is old gmake style with thousands of rules, where nearly nobody is able to maintain it. And hundreds of scripts for the builds on solaris. Windows is acutally not really good supported. It's a cygwin with all the scripts and a lot of trouble as well. And you have few experts, on which the whole build process rely on.
 
> , is it a custom solution or is it based on well-maintained
> projects, is it targeted to a single or multiple platforms/programming
> languages, and last but not least, is it documented as you would expect
> cmake to be?.

No definitivly not, and therefor I try to make this clear here, that there is no alternative to switch to a modern build proceses. But, you now I am under fire and every day I blow off time lets people convince, that this way is as difficult as the old one.

> 
> Good luck tomorrow with your presentation. I hope it all goes as expected.

Thanks :-)



More information about the CMake mailing list