[bug] Setting CMAKE_TOOLCHAIN_FILE to conan_toolchain.cmake make vscode-cmake-tool not work.

I use VSCode to write a executable. And I use CMakeDeps and CMakeToolchain generators. After setting CMAKE_TOOLCHAIN_FILE to conan_toolchain.cmake, the command CMake: Run Without Debuging does not work. I have no idea it’s due to Conan or vscode-cmake-tool. But when removing CMAKE_TOOLCHAIN_FILE, everything works fine.

Environment Details (include every applicable attribute)

• Operating System+version: Ubuntu 22.04 (docker)
• Compiler+version: g++ 11.2
• Conan version: 1.47
• Python version: 3.10

Steps to reproduce (Include if Applicable)

1. Start a new docker and use VSCode to open it.
2. Start a new project with conan and with CMakeDeps and CMakeToolchain generators.
3. Set CMAKE_TOOLCHAIN_FILE to conan_toolchain.cmake above project(demo) (using cmake_kits.json is the same).
4. Put find_package(something REQUIRED) to CMakeLists.txt and it can compile with CMake: Build but CMake: Run Without Debuging.

Logs (Executed commands with output) (Include/Attach if Applicable)

No log

[memsharded]

Yes, these integrations are relatively stable now, but still experimental, it is expected that they keep improving from release to release, fixing bugs, etc., but might not get backports patches to older releases, because that experimental status.

[Kidsunbo]

Hi @memsharded I found that with Conan 1.48, cmake tools for VSCode works perfectly even though it still doesn’t work with Conan 1.47. But it’s enough that it works with newer version. Thanks.