[CMake] Version compatibility?

[Vladimír Vondruš]

In my case I'm going through changelogs to see what is added in which version. For example I switched to the imported target workflow recently and need to keep backward compatibility all the way back to 2.8.12 (because Ubuntu LTS). There are a lot of features that were added later and are crucial (ALIAS targets, interface compatibility...), so I somehow need to add version-specific workarounds to make the projects working on 2.8.12.

The changelogs are pretty useful source of information, but it would be great to have the information directly in the docs to avoid trial and error.

Regards
mosra

______________________________________________________________
> Od: Nils Gladitz <nilsgladitz at gmail.com>
> Komu: Craig Scott <craig.scott at crascit.com>, "Johannes Zarl-Zierl" <johannes.zarl-zierl at jku.at>
> Datum: 25.04.2016 15:51
> Předmět: Re: [CMake] Version compatibility?
>
> CC: "cmake at cmake.org" <cmake at cmake.org>
>On 04/25/2016 02:29 PM, Craig Scott wrote:
>> I personally have found myself having to look up to his sort of 
>> version info a lot lately. It sounds like others do too. Perhaps a 
>> more sustainable approach would be to include the version details in 
>> the CMAKE docs themselves. For each command, module, variable, etc. 
>> it's documentation could state the version it was added. Some may 
>> warrant further info for version(s) where significant changes were 
>> made (eg keywords added to a command). Realistically, it would have to 
>> be done progressively and obviously with agreement from the Kitware 
>> side. It would only work if it became part of the change process 
>> whereby any new features or changes must include such version details. 
>> It would be interesting to hear what Kitware think of the idea. Any 
>> chance?
>
>I've also made use of such information from time to time but I think it 
>has been the exception and it doesn't normally come up during my regular 
>development workflow.
>
>I assume for most projects there is a single 
>cmake_minimum_required(VERSION).
>Which means to see what is and what isn't available I only have to check 
>that specific version's documentation.
>
>I am curious as to what kind of use case results in having to require 
>cross-version information as provided by the compatibility matrix "a lot".
>
>Nils
>
>
>----------
>
>-- 
>
>Powered by www.kitware.com
>
>Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>
>Kitware offers various services to support the CMake community. For more information on each offering, please visit:
>
>CMake Support: http://cmake.org/cmake/help/support.html
>CMake Consulting: http://cmake.org/cmake/help/consulting.html
>CMake Training Courses: http://cmake.org/cmake/help/training.html
>
>Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
>Follow this link to subscribe/unsubscribe:
>http://public.kitware.com/mailman/listinfo/cmake
>