[feature] include CMAKE_<LANG>_COMPILER in generated CMakePresets.json

[melak47]

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?

• I've read the CONTRIBUTING guide

[memsharded]

Hi @melak47

Thanks for your feedback.

This was tried in the past in:

• Define compiler variables in CMakePresets.json #16762

and it had to be reverted. See:

• [bug] When cross-compiling with android-ndk, CMake cache_variables are not set in the CMakeCache.txt every other run #16960
• Test to reproduce #16960 #16966
• Add test for #19960 #16974

It is pending to try again and do further investigation if this can be done, but it is not as trivial as it seems

[melak47]

I see, thanks for finding that.
For now there is a workaround for the vscode/cmake-tools issue, and it might get solved on their side eventually.