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

[Eric Noulard]

2010/11/24 David Cole <david.cole at kitware.com>:
> 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.

+1 for this, even if it does not solve all "evolution" problem like
when IF command was added the

IF(TARGET ...) or IF(POLICY ...)

I don't remember when (may the 2.4 --> 2.6 switch)
basically IF command existed before and after the evolution but its
capability was enhanced.

May be adding a list of version for each command may be covering this

like
IF --> start, 2.4.8, 2.6.2, 2.8.3

meaning that IF command was there since "start" and evolved in
2.4.8, 2.6.2, 2.8.3 releases.

If ones want to know the difference one can go and pick up each such release
in order to "generate" documentation diff.

May looks fancy but not knowing that XXXX command has not
all the feature it currently has is  interesting too.

Note with that kind of list I can automatically
generate a per-command diff of documentation using my private CMake
binary collection :-]
-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org