[CMake] documentation for previous cmake versions
Bill Hoffman
bill.hoffman at kitware.com
Wed Feb 28 16:54:05 EST 2007
Alan W. Irwin wrote:
> On 2007-02-28 22:03+0100 Eric Noulard wrote:
>
>> 2007/2/28, Alexander Neundorf <a.neundorf-work at gmx.net>:
>>> >
>>> > History:
>>> > New Since 2.4.0 New INSTALL macro
>>> > New Since 2.4.4 Added the INSTALL(DIRECTORY ...) support
>>>
>>> E.g. for FIND_PACKAGE() the COMPONENT feature was added in 2.4.4.
>>> This might become a long list when done completely for all commands.
>>>
>>
>> You are right but in at first glance I would say that those
>> per-MACRO history list may not be as long as you think.
>> Very new feature on just the same MACRO is not so common,
>> of course I may be wrong.
>>
>> Even if the history is long I'll find it more usable than separate
>> browsing of different version, but of course that's my point of view.
>
> I think that is a lot of work so we will get nothing as a result from our
> time-constrained CMake developers.
>
> What I would like to see is the results of cmake --help-full output to an
> ascii file and committed under CVS control for every historical
> release in
> say the 2.4.x series up to 2.4.6. That would only take a small one-time
> effort by the CMake developers to build each of the 6 cmake releases
> in the
> 2.4.x series and make those 6 commits. After that initial effort for the
> historical releases, this would only have to be done once after each
> official release. Suppose that file was called Docs/help_full.out. Then
> browsing that file in
> http://www.cmake.org/cgi-bin/viewcvs.cgi/Docs/?root=CMake automatically
> gives the user any diff between any version.
Hey, that's a great idea! I think i might be able to do that with a
little modification to
my release scripts. There is also the Changelog.manual file that should
have most of that
stuff, but docs for each version is a cool idea.
-Bill
More information about the CMake
mailing list