[cmake-developers] [CMake 0012363]: Single-line status+result messages (echo -n, \c)

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
====================================================================== 
http://www.cmake.org/Bug/view.php?id=12363 
====================================================================== 
Reported By:                Christopher Sean Morrison
Assigned To:                
====================================================================== 
Project:                    CMake
Issue ID:                   12363
Category:                   CMake
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2011-07-27 14:43 EDT
Last Modified:              2011-07-27 14:43 EDT
====================================================================== 
Summary:                    Single-line status+result messages (echo -n, \c)
Description: 
CMake's simplified build reporting is great, but the ability to display the
results of configuration testing seems very limited.  Similar to autotools
configuration testing, our CMake build tests various platform characteristics. 
Right now, the user is notified that a test is about to commence with
message(STATUS, "Testing feature blah") and then the result with another
message(STATUS, "Testing feature blah: failed").

That of course annoyingly leads to two lines for every feature tested (which is
hundreds of tests for a large complex package).  It would be great if we could
display that message in two parts, once before the test with a label, once after
with the result.

That is akin to "echo -n Testing feature blah: " && echo "failed" or
AC_MSG_CHECKING([feature blah]) && AC_MSG_RESULT([failed]) in autotools/m4
parlance.

For platforms/output configurations that can display them sequentially, you get
nice pretty-printed output.  For others (e.g., MSVC) where only single-line
output is supported, you'd get that as either two lines or line-buffered until
the result is ready.


Additional Information: 
We could only print the latter message, but some tests take a while so
preliminary feedback for environments where that is possible is highly
desirable.  I tried using the old '\c' character on message() but as you
probably know, that reports it is an invalid escape sequence.

====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-07-27 14:43 Christopher Sean MorrisonNew Issue                             
      
======================================================================