View Issue Details [ Jump to Notes ]

[ Print ]

Project

Category

View Status

Date Submitted

Last Update

0012363

CMake

public

2011-07-27 14:43

2016-06-10 14:31

Reporter

Christopher Sean Morrison

Assigned To

Kitware Robot

Priority

normal

Severity

feature

Reproducibility

N/A

Status

closed

Resolution

moved

Platform

OS Version

Product Version

CMake 2.8.4

Target Version

Fixed in Version

Summary

0012363: 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.

Tags

No tags attached.

Attached Files

Relationships

Notes
(0030283) David Cole (manager) 2012-08-11 11:38	Sending old, never assigned issues to the backlog. (The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...) If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^] It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.

(0041871) Kitware Robot (administrator) 2016-06-10 14:28	Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.

Issue History
Date Modified	Username	Field	Change
2011-07-27 14:43	Christopher Sean Morrison	New Issue
2012-08-11 11:38	David Cole	Status	new => backlog
2012-08-11 11:38	David Cole	Note Added: 0030283
2016-06-10 14:28	Kitware Robot	Note Added: 0041871
2016-06-10 14:28	Kitware Robot	Status	backlog => resolved
2016-06-10 14:28	Kitware Robot	Resolution	open => moved
2016-06-10 14:28	Kitware Robot	Assigned To	=> Kitware Robot
2016-06-10 14:31	Kitware Robot	Status	resolved => closed