On Wed, Apr 25, 2012 at 1:55 PM, Stephen Kelly <[email protected]> wrote:
> The idea is that if you use cmake_maximum_required(2.8.8) and attempt to use
> a feature or API introduced in 2.8.9, CMake would report an error.
I don't think that's the opposite of a minimum required version, I
think that *is* one. The same error could be generated just from
cmake_minimum_required(VERSION 2.8.8)
because CMake 2.8.9 would know that it is possible users may run 2.8.8
on the project.
Either way it will be very difficult to implement and maintain. Even
if we taught every feature to check the version projects might do
if(NOT ${CMAKE_VERSION} VERSION_LESS 2.8.9)
# use 2.8.9 feature
endif()
and it would be very hard for CMake code running inside the condition
to detect that it is okay.
Project testing infrastructure (e.g. nightly dashboard builds) should
include runs using the oldest CMake allowed to ensure things work
without newer features.
-Brad
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
