Bob Brown

Allow alterations to the $PATH in an environmentSetupScript to take effect before searching for the CMake executable

3

### Discussed in https://github.com/microsoft/vscode-cmake-tools/discussions/2299 Currently the extension searches for the CMake executable before `environmentSetupScript` is evaluated. In the event that the setup script alters the $PATH, those changes won't be...

Issue with configuration

13

Hi, After working with CMake on VS 2022, it is time to check VSCode... (the real reason that I need the project on Linux too :-)) After a lot of...

How to debug using sudo

1

### Discussed in https://github.com/microsoft/vscode-cmake-tools/discussions/2445 Originally posted by **Giancarlo-Ma** March 20, 2022 Some code are required sudo permission, so when click the debug button, It just shows that I have no...

Improve the experience around missing CMakeLists.txt files

6

I have a multi-root workspace, where one of the roots is for Python code, one is for CMake, and one is just for a reference to common headers that are...

### Brief Issue Summary The Windows CI tests take a lot longer than the linux/mac tests (about 4x). Part of this is because most tests use the Visual Studio generator...

Cpptools configuration issue after building

18

I'm not sure if I should open a new issue, but I also have this issue. It happens randomly and there's nothing special in the C++ extension logs. IntelliSense works...

VS build environment is not set when using clang

3

So what is the trick to get VSCode to call vcvars? My preset: ``` { "name": "win-ninja-release", "displayName": "win-ninja-release", "description": "Ninja generator release", "generator": "Ninja", "binaryDir": "${sourceDir}/build/ninja/release", "inherits": ["ninja-general" ,...

### Brief Issue Summary PR #2683 works around a problem we have with our tests. When a setting is changed, we call `update` from the VS Code API. This method...