Hi Brad,
I was thinking of coming back to issue of the deprecation and author
message options, now that CMake 3.4 has been released, is now a suitable
time for it?
I was thinking of ideas and one came to mind, how does the following sound?
We modify cmake::IssueMessage to check the relevant CMake variables to
determine if the message should be output and at which level, we try to
get the script provided values if possible but handle the case where we
can't. We also modify IssueMessage to use
cmSystemTools::SetFatalErrorOccured (or SetErrorOccured if that's
preferred) if a warning has been turned into an error. Finally we modify
the users of IssueMessage, to check the error occured state using
cmSystemTools, and use that to determine if an error has occured (rather
than the message level going into IssueMessage) and if the return value
should be changed accordingly.
Cheers,
Michael
--
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-developers
