[CMake-Promote] not so nice cmake comments

[Bill Hoffman]

Brandon J. Van Every wrote:
>
> The antidote to this, is to show people why it's more expensive to 
> cobble up your own scripts, over the long haul.  If that is indeed 
> provable.  A white paper.  And, it's important to get that white paper 
> in front of a manager / decisionmaker, who can hold programmers 
> accountable for how they're evaluating.  That implies slicking up the 
> Kitware website to be manager friendly.  It should have a "Case 
> Studies" section that's easily found by top level navigation.

Well, perhaps we can start with an expanded wiki section on this, and
include some stats from places like this:

http://blog.qgis.org/?q=node/16

Alex are there any stats from the KDE switch?


If we can get the information correct in the wiki we have some software
that can covert wiki to web pages.  This would give it a more polished
look.  But the first step would be to create the content in the WIKI.

So, if you are a linux only developer why use cmake?

1. it is fast
2. there is only one build language, not m4+shell, plus make, etc.
3. if you ever need to port in the future
4. it is easier to create simple projects
5. KDE uses it

Tanner has a nice article on this here http://www.linux-mag.com/id/2559/

So, I guess this involves making this stuff nicer:

http://www.cmake.org/Wiki/CMake_Projects

Also, I would think at this point in time, that page would have more
entries.  How do we get people to add projects?

-Bill