You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, VSCode's cmake-tools extension seems to check for "CMAKE_<C/CXX>_COMPILER": "cl" being present in the preset to determine if it should set up the vcvars environment for your build tasks.
When using the CMakeDeps + CMakeToolchain generators (with the Ninja CMake generator),
the preset generated by conan does not set those cache variables (because they are set in the toolchain file).
As a result, cmake-tools does not set up the environment, meaning you have to activate the environment manually before starting VSCode, or write another preset inheriting from the conan generated preset to add the variables.
I was wondering if these variables could just be included in the preset to avoid this?
Have you read the CONTRIBUTING guide?
I've read the CONTRIBUTING guide
The text was updated successfully, but these errors were encountered:
What is your suggestion?
Currently, VSCode's cmake-tools extension seems to check for
"CMAKE_<C/CXX>_COMPILER": "cl"
being present in the preset to determine if it should set up the vcvars environment for your build tasks.When using the CMakeDeps + CMakeToolchain generators (with the Ninja CMake generator),
the preset generated by conan does not set those cache variables (because they are set in the toolchain file).
As a result, cmake-tools does not set up the environment, meaning you have to activate the environment manually before starting VSCode, or write another preset inheriting from the conan generated preset to add the variables.
I was wondering if these variables could just be included in the preset to avoid this?
Have you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: