[CMake] Documentation strategy

[Philippe Fremy]

Brandon Van Every wrote:
> My conclusion is
> that Kitware doesn't have the resources to address these things, and
> the community has to find a way to do it.

If I understood correctly, kitware does not do any money off CMake. They
just need CMake to be good and usable, so that they can make money with
their other products. That makes it difficult for them to indeed commit
resources to that kind of problem.

It's unfortunate.

>  The
> community has to devise a better infrastructure, or this situation
> will persist indefinitely.


>> That's probably covered in the book, but I find it strange that you need
>> a book to be able to use an open source tool like CMake. Maybe I am too
>> used to high quality documentation ?
> 
> Not at all.  The vast majority of mature commercial products out
> there, open source ones included, have high quality electronic
> documentation.  CMake can either provide that like everyone else does,
> or fall by the wayside over time.  There's too much competition out
> there for people to accept this situation indefinitely.

You are burying CMake a bit quickly. How many build source tools out
there are easy to use, can generate Visual Studio projects or Makefiles,
are fully cross-platform and work well ?

I am no expert, but I understand that CMake is the only one out there
that meet all these requirements.

Most other build tools are usually a replacement of make. Good
replacement for most of them, but replacing make does not generate a
Visual Studio project.

	regards,

	Philippe