Sure but how would CMake solve it?
It would have to keep a backtrace of all properties when a target is created.
Or at least all properties involved in the list of sources. You need a
backtrace (or some other way to store a source location) in order to find a
source location. That seems kinda
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.
The problem right now is that backtraces are memory intensive. See this issue
for a discussion about
Thanks for the link. I'll respond there.
We still have backtraces in our fork, so I'll continue using them for now. Ben
had a good point though. I think for our use case, the last value is the one
needed.
I don't think I can go into more detail other than we want to let the user
navigate to
We're (Microsoft) investigating tighter integration with CMake -Server and the
IDE.
One of the things we need is to be able to get the location of where a property
is set.
CMake has a backtracing capability but it looks to me like properties don't
actually keep track of their set location.
I
Tobias, can you make sure it still supports passing the source directory too?
Otherwise we’ll have to have version dependent arguments that we pass to CMake
server.
From: Isaiah Norton [mailto:isaiah.nor...@gmail.com]
Sent: Tuesday, January 23, 2018 7:16 AM
To: Brad King
Cc: Tobias Hunger ; Ric
If you have the build directory, can’t you just parse the CmakeCache.txt?
CMAKE_HOME_DIRECTORY in the cache is the source folder. Seems easier than
writing something to talk to CMake server.
From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On Behalf Of
Isaiah Norton
Sent: Mon
