On Thu, Jul 9, 2015 at 1:35 PM, Clifford Yapp <cliffy...@gmail.com> wrote:
> 3. Have one or a number of variables that will hold in memory all the > text written out by message (CMAKE_MESSAGES, CMAKE_STATUS_MESSAGES, > CMAKE_ERROR_MESSAGES, etc.) so the CMakeLists.txt file can create log > files reflecting what the user is seeing on the console window. Actually, thinking about that, what's really needed is not an in-memory log but a way to specify log files, since an unexpected crash or exit is not a situation under which such in-memory logs could be reliably written to disk. So it would instead need to be CMAKE_STATUS_MESSAGE_LOG, CMAKE_ERROR_MESSAGES_LOG, etc. which would hold paths to which messages would be copied before being written to stdout/stderr. Cheers, Cliff -- 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
