[CMake] providing library information, what's the cmake way

Alexander Neundorf a.neundorf-work at gmx.net
Thu Nov 25 15:54:01 EST 2010


On Thursday 25 November 2010, Johannes Zarl wrote:
> On Wednesday 24 November 2010 19:03:21 David Cole wrote:
> > On Wed, Nov 24, 2010 at 12:58 PM, Tyler Roscoe <tyler at cryptio.net> wrote:
> > > On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
> > >> On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer <eike at sf-mail.de> 
wrote:
> > >> > So I think it is _really_ necessary to go through all the CMake
> > >> > documentation items and add a line about when which feature was
> > >> > added.
> > >>
> > >> Adding that information in the documentation would be good, I agree.
> > >> (Although quite time consuming and costly for somebody...)
> > >
> > > Perhaps a good compromise is simply to add version information to all
> > > new CMake commands/variables/properties that are added henceforth?
> > >
> > > Thanks,
> > > tyler
> >
> > That does sound like a good idea.
>
> From the information in http://www.cmake.org/Wiki/CMake_Released_Versions
> and using some shell-scripts to create the diffs between all
> "neighbor-versions", it's not too much work to create a compatibility
> matrix for the documented features.
>
> I took the liberty and compiled such a compatibility matrix here:
> http://www.cmake.org/Wiki/CMake_Version_Compatibility_Matrix
>
> It's a draft and does not (yet) contain information about properties and
> variables, but if this idea receives general consent I could complete the
> information.
>
> What do you think? Is this worth the effort, or would no one ever bother to
> update the information?

I think it's cool :-)
I for one update the http://www.cmake.org/Wiki/CMake_Released_Versions page 
manually after each release.

Alex


More information about the CMake mailing list