Re: [cmake-developers] cmake Xcode bug clobbering -ObjC/-ObjC++ flags

2015-10-18 Thread Gregor Jasny via cmake-developers
On 15/10/15 19:16, Davy Durham wrote:
> Bug filed here: https://cmake.org/Bug/view.php?id=15794
> Patch file against git master HEAD attached to this email.
> 
> Acceptable?

I responded to the bug report itself:
https://cmake.org/Bug/view.php?id=15794#c39625

Two questions for the CMake developers:

1) I'd like to add an Unit Test for the ExtractFlagRegex function. Could
you please tell me where to add it?

2) Do you consider ExtractFlagRegex generic enough to be moved somewhere
else?

Thanks,
Gregor
-- 

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


[cmake-developers] [CMake 0015798]: add_test page ought to specify what constitutes a valid test

2015-10-18 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=15798 
== 
Reported By:Joachim Wuttke
Assigned To:
== 
Project:CMake
Issue ID:   15798
Category:   Documentation
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2015-10-18 15:35 EDT
Last Modified:  2015-10-18 15:35 EDT
== 
Summary:add_test page ought to specify what constitutes a
valid test
Description: 
https://cmake.org/cmake/help/v3.4/command/add_test.html describes the command
»add_test« which has a parameter »COMMAND« to »specify the test
command-line«.

It would be appropriate to provide an explanation (or/and a link to an
explanation) of what constitutes a valid test command.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-10-18 15:35 Joachim Wuttke New Issue
==

-- 

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

Re: [cmake-developers] Add command line options for deprecation message control

2015-10-18 Thread Michael Scott

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