On 04/15/2014 11:39 AM, Stephen Kelly wrote:
>> I think we should reverse our earlier decision and go ahead and add
>> an error whenever a feature is requested that we do not know *is*
>> supported for the current {id, version}.
>
> Yes, I think that makes sense. Such an error can be relaxed in the future if
> desired.
The change proposed here:
Features: Decay language flag if requested is not available.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=93e7729d
makes the CXX_STANDARD target property specify a request to be
decayed rather than a requirement. What if a project really wants
to require a given standard level?
Perhaps we can have a feature name like "cxx_std_11" to require a
given standard level with an error if it is not available.
Steve, how did you envision CXX_STANDARD, CXX_EXTENSIONS, and
COMPILE_FEATURES to be used together by a project?
Thanks,
-Brad
--
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/cgi-bin/mailman/listinfo/cmake-developers
