obvious. Okay maybe not a backtrace then, but
just the top of the trace.
-Original Message-
From: cmake-developers On Behalf Of Tobias
Hunger
Sent: Thursday, February 15, 2018 7:38 AM
To: Ben Boeckel
Cc: CMake Developers
Subject: Re: [cmake-developers] Cmake-server question
On Thu
On Thu, Feb 15, 2018 at 3:18 PM, Ben Boeckel wrote:
> On Wed, Feb 14, 2018 at 19:19:39 +0100, Paweł Rutka wrote:
>> I would like to ask about some important feature:
>> Is there any possibility to provide form Cmake Server side location of
>> command that generate the target? The Use Case is as fo
On Wed, Feb 14, 2018 at 19:19:39 +0100, Paweł Rutka wrote:
> I would like to ask about some important feature:
> Is there any possibility to provide form Cmake Server side location of
> command that generate the target? The Use Case is as follow:
> In IDE you want to, after Class creation, automat
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 da
On Wed, Feb 14, 2018 at 7:27 PM, Rich Chiodo via cmake-developers
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 backtr
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
