Bob Brown

@alan-wr The environment created for your build is not shared with the environment used to resolve VS Code settings. That's probably why it does not appear to work.

Are you saying that running a build is reconfiguring CMake? I wouldn't expect the `message` command to evaluate during a `cmake --build` command. If you run those same two `cmake`...

> If I run both command in a terminal, the behavior is the same as if I'd invoke them respectively using `ctrl+s` shortcut and `⚙Build` button. Just to confirm, when...

This was determined to be an upstream issue. Closing.

The way to bump the priority of this is to click the 👍 on the first comment.

Visual Studio supports this. You go to Project -> CMake Workspace Settings and add `"sourceDirectory": [ "dir1", "dir2", ...]` to the json file.

> It is best to support ignoring cmake projects under a certain folder, so as to avoid too many projects being included in a single workspace and it(build) is difficult...

The extension has some heuristics to guess the debugger configuration based on the compiler being used. When this guessing fails, you can force whatever settings you need by using the...

Right now, the extension does not query the compiler for supported cross-compile targets. The command is essentially `gcc -v`. I believe this only reports the host triplet. @lygstate, I believe...

I don't believe that the progress box has an effect on the output delay. I think it's more likely to be our problem matchers slowing it down because your machine...