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