-
Notifications
You must be signed in to change notification settings - Fork 462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
env in presets not work and cmake.cmakePath not work #4218
Comments
Given that the environment variable doesn't work, I temporarily replaced it with a defined value, and then it still failed to configure.
I have a feeling that cmake tools is completely broken, and even if you back off and temporarily fix one problem, you'll still be faced with the next one |
@vipcxj Thank you for your github issue! We would like to reproduce your issue, could you give us a repro steps? |
@vipcxj Does this reproduce in the most recent pre-release version of the extension? |
As a contingency, I've changed all relative paths to absolute ones, but I've realized that my other problem may be due to the same cause #13124 |
@vipcxj Following up on whether the issue reproduces in the most recent pre-release version? |
Brief Issue Summary
This problem happened in the last few days.
cmake
and that it was fine before. I could also get the result by typingcmake --version
directly in the terminal. However, to fix the problem, I changed it to the absolute path of cmake, and the problem was temporarily solved"CMAKE_TOOLCHAIN_FILE":"$env{VCPKG_ROOT}/scripts/buildsystems/vcpkg.cmake",
However, according to the output window, "$env{VCPKG_ROOT}/scripts/buildsystems/vcpkg.cmake" is resolved to "/env{VCPKG_ROOT}/scripts/buildsystems/vcpkg.cmake", which leads to configuration failure. But I tried it in the terminal and the environment variable VCPKG_ROOT was configured correctly. For this I tried restarting vscode, restarting vscode-server, both no effectCMake Tools Diagnostics
Debug Log
Additional Information
From the Debug log you can see that vscode does get the value of the environment variable VCPKG_ROOT, so I think this should be the bug
The text was updated successfully, but these errors were encountered: