Hi Rich, FYI there is discussion about providing backtraces from the server to clients here:
https://gitlab.kitware.com/cmake/cmake/issues/17539 It was originally done in CMake 3.10.0 but caused major memory bloat and so was reverted. > One of the things we need is to be able to get the location of where > a property is set. Threading that through everywhere for arbitrary properties will cause too much memory usage. `cmTargetInternals` already has dedicated fields for backtraces of specific properties. Something like that could be added for the properties you need. Can you provide more details about the use case? -Brad -- 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: https://cmake.org/mailman/listinfo/cmake-developers
