It's been my understanding that calling message() without STATUS, WARNING, or ERROR was a STATUS by default. Considering that when I use both WARNING and ERROR the output looks different. Dialogs will appear and such. Are message() and message( STATUS ) not identical? If not, what are the differences? Why are they different?<br>
<br><div class="gmail_quote">On Wed, Mar 25, 2009 at 9:51 PM, Michael Jackson <span dir="ltr"><<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Would it be possible to do what compilers do: prepend status lines with "STATUS", warning with "WARNING" and error with "ERROR". That makes it easier to grep if needed and may help pull attention to each type of output.<br>
<br>
Just thinking out loud...<br>
<br>
---<br>
Mike Jackson <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><div><div></div><div class="h5"><br>
<br>
On Mar 25, 2009, at 10:43 PM, Philip Lowman wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Mar 25, 2009 at 9:59 PM, Clinton Stimpson <<a href="mailto:clinton@elemtech.com" target="_blank">clinton@elemtech.com</a>> wrote:<br>
<br>
The intent I get from the documentation is that its a message that is meant to say something important. It pops up in the CMakeSetup, shows up in the error section of ccmake, and stdout of cmake.<br>
<br>
Maybe cmake-gui should show it bold or something instead of red, which I also think of as an error.<br>
<br>
The color might be a minor problem but another is that the messages will get buried if there is a lot of STATUS.<br>
<br>
As much as I hate the popup in CMakeSetup I have to wonder if burying a warning that used to emit a popup so the user may have to scrollback to even see it is necessarily a good change.<br>
<br>
Perhaps a popup should be added again (obviously leaving some kind of bold/colored output in place). A simple checkbox on the bottom that says "Skip future warning messages during this configure" or something like that would be far better than how CMakeGui handles the case of multiple popups becoming disruptive.<br>
<br>
-- <br>
Philip Lowman<br>
</blockquote>
<br></div></div><div><div></div><div class="h5">
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br>