[cmake-developers] [PATCH] stage/compact-status-log

Chuck Atkins chuck.atkins at kitware.com
Wed Sep 24 10:11:56 EDT 2014


>
> What happens if something else occurs in between that prints
> a message?  Do we tolerate
>
>  -- Doing something-- Unrelated Message
>  - Result
>
> instead of
>
>  -- Doing something
>  -- Unrelated Message
>  -- Doing something - Result
>

Sure, why not?  There's no requirement to use the NOENDL, it would just be
an additional option.   The places where this happens is most in the
Modules/* code for system introspection.  If the code path allows for
extensive messaging in between status messages, then just don't use the
NOENDL option.  It would be entirely optional and up to whomever is writing
the CMake code whether or not to use it.  We could easily use it in most of
the system introspection modules without worry though.



> Also the approach needs to work in ccmake where only one
> status line is shown at a time.
>

Sure it would.  Nothing monumental would need to change though.  It
currently output's every message separately, but it could just output the
current message append to the previous message and then when an endline is
found then clear the append message buffer.

I'm not saying it should be done this way, just offering an alternate
approach that might be more flexible.  The details and tests would still
need to be worked out.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20140924/8b4a0afb/attachment-0002.html>


More information about the cmake-developers mailing list