[CMake] Adding Cmake version in online documentation

Nils Gladitz nilsgladitz at gmail.com
Thu Nov 10 02:40:01 EST 2016


On 11/09/2016 09:06 PM, Ruslan Baratov wrote:

>
> So why the project in the middle of the migration process is not a valid
> case? It is maintained but the exact migration step is paused, but I
> have an intention to improve the code in future. Anyway even if the
> project is no longer maintained, then what we have? We have
> `cmake_minimum_required` with the version that fits **features** the
> code has and `cmake_policy` to control the **behavior** of different
> cmake versions.

Temporary use during migration to a new CMake version is one of the use 
cases explicitly mentioned in the documentation.
But when you say you might migrate some time in the future that makes it 
sound like you aren't actually in the process of migration but are 
rather looking for some loophole.

>
>> Or as I said cmake's testsuite.
>>
>> If you insist on actual code e.g. this is part of the tests that I
>> wrote for CMP0054:
>> https://cmake.org/gitweb?p=cmake.git;a=blob;f=Tests/RunCMake/CMP0054/CMP0054-NEW.cmake;h=23a912476024ba09fcf741e04f999b64a6e91450;hb=refs/heads/master
>>
> The internal CMake stuff is out of the scope of discussion. If policies
> are the internals why do we need them in the documentation?

Well you could have excluded the case when I brought it up initially 
preferably before asking for code.
I don't have any unmaintained public projects in mind that I could link to.
But then again as I said before the code itself is entirely irrelevant; 
what counts is the context.

Nils


More information about the CMake mailing list