We get some talk and backtraces will not probably either way can handle multiple scenerios with functions and macros... But currenly I think Cmake do not have any knowledge how to match for example Variables used in initial call and one passed at the bottom to add_executable (seems like all this data is lost while processing file, backtrace is recored but it do not record params so you cannot backmatch anything usefull).
But this topic should probably be ask to someone in Cmake dev team how It could be resolved. Regards, Pawel 2018-02-15 10:28 GMT+01:00 Tobias Hunger <tobias.hun...@gmail.com>: > On Wed, Feb 14, 2018 at 7:27 PM, Rich Chiodo via cmake-developers > <cmake-developers@cmake.org> wrote: > > This would require backtraces, I believe, on every property so you can > trace > > all the properties back to where they’re defined. I need this too for > Visual > > Studio to support adding files as well. > > I disagree: Using backtraces for this is a pretty ugly hack! > > IDEs should not need to examine backtraces for a simple and common > task like adding files to a target! Ideally server-mode would have a > way to ask cmake where to add a source into a target and that will > then tell you the file/line/column to add the file into. > > Best Regards, > Tobias >
-- 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
