Bob Brown

@bamurtaugh the problem appears to be that there is no symlink from `ctest` -> `/opt/cmake/bin/ctest` which I think was already stated. To deal with path issues like this, CMake Tools...

@ibis-hdl I see this PR to add the symlink: https://github.com/microsoft/vscode-dev-containers/pull/1598 @bamurtaugh any chance you can merge it in? cc: @michaelbprice

> There is some value in having a distinct CMake devcontainer template in addition to a generic C++ one. The same might be also true for a Make container, but...

Just to confirm, you're talking about "multi-root" workspaces, and not a single folder with multiple CMake projects in subfolders of that single folder in the workspace, right?

I got some clarification from @TheJCAB about the workspace: * multi-root with 4 folders * folder 1 has the CMake project with CMakePresets.json in it * folders 2-4 are not...

The difference between VS and VS Code is that VS assumes the compiler is cl.exe and VS Code does not. VS will happily set the `CMAKE_C|CXX_COMPILER` to `cl.exe` automatically for...

> CMake DOES find cl.exe, but still the error is there... Can you run the C++ extension's Log Diagnostics command this time `C/C++: Log Diagnostics`? It looks like you updated...

Just wanted to also note that I did try this out on your attached project and am unable to reproduce the problem once the cacheVariables are added. I understand that...

That path looks correct. It's essentially the same as mine and mine works. `C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31627\include` cpptools is using it according to the log, but it still can't find...

That's weird because CMake Tools should be running devcmd.bat for you automatically (it does for me with your project) and storing the INCLUDE variable to add to the build environment...