|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0012373||CMake||Documentation||public||2011-07-31 06:13||2016-06-10 14:31|
|Assigned To||Kitware Robot|
|Target Version||CMake 2.8.12||Fixed in Version|
|Summary||0012373: Specify version changes with each commands/variables|
|Description||Documentation is pretty efficient but if you work with different CMake versions, you almost always end up using a feature or a variable that was not available in previous versions (eg. 2.8.4 against 2.8.2, I'm not talking about 2.6 to 2.8 step)|
New commands, variables, or command parameters are often added between versions. When this happens it would be nice to have it written in the doc so that users know not to use a specific feature when they are targeting a specific cmake version.
|Tags||No tags attached.|
Eric NOULARD (developer)
There is a nice Wiki page for that:
but it would definitely be interesting to have a "since x.y" inside the doc.
Jérôme Vizcaino (reporter)
That is right. I work at a place with no internet connection and the only thing I have is the manual (this is a Debian package).
Unless the Debian guys package the wiki, I'm stuck :)
David Cole (manager)
Sending old, never assigned issues to the backlog.
(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)
If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]
It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
Brad King (manager)
IMO having to specify the version in which every little thing was changed/added will be a huge maintenance burden. The information will accumulate and clutter the documentation with version references that become less useful over time.
Since this was first filed we've started posting documentation for each version separately on the web site:
Just read the docs corresponding to your cmake_minimum_required(VERSION).
If you don't have net access then just install minimum version of CMake you require and don't use a newer version.
David Cole (manager)
These bugs were deferred from target version 2.8.10 to 2.8.11 based on the responses to this email thread on the CMake developer's mailing list:
Kitware Robot (administrator)
Resolving issue as `moved`.
This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.
|2011-07-31 06:13||Jérôme Vizcaino||New Issue|
|2011-07-31 14:32||Eric NOULARD||Note Added: 0027132|
|2011-07-31 14:58||Jérôme Vizcaino||Note Added: 0027133|
|2012-08-11 11:38||David Cole||Status||new => backlog|
|2012-08-11 11:38||David Cole||Note Added: 0030288|
|2012-08-14 11:23||David Cole||Status||backlog => new|
|2012-08-14 11:23||David Cole||Target Version||=> CMake 2.8.10|
|2012-08-14 11:43||Brad King||Note Added: 0030645|
|2012-10-18 11:16||David Cole||Target Version||CMake 2.8.10 => CMake 2.8.11|
|2012-10-18 11:17||David Cole||Note Added: 0031265|
|2013-05-17 09:33||Robert Maynard||Target Version||CMake 2.8.11 => CMake 2.8.12|
|2016-06-10 14:28||Kitware Robot||Note Added: 0041876|
|2016-06-10 14:28||Kitware Robot||Status||new => resolved|
|2016-06-10 14:28||Kitware Robot||Resolution||open => moved|
|2016-06-10 14:28||Kitware Robot||Assigned To||=> Kitware Robot|
|2016-06-10 14:31||Kitware Robot||Status||resolved => closed|
|Copyright © 2000 - 2018 MantisBT Team|