er
navigate to where different things are set.
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Wednesday, January 31, 2018 11:43 AM
To: Rich Chiodo ; CMake Developers
Subject: Re: [cmake-developers] Adding backtraces to every command
Hi Rich,
FYI there is d
On Wed, Jan 31, 2018 at 18:53:39 +, Rich Chiodo via cmake-developers wrote:
> 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 capabil
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 locat
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
