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
{{ message }}
Repository navigation
Setting PATH In "cmake.environment" Causes ENOENT Failures #2855
... then re-select that kit (so the field gets read), configure, it completes fine:
...
[cmake] -- Configuring done
[cmake] -- Generating done
[cmake] -- Build files have been written to: /home/<pathToProject>/build
Extension version: 1.12.27
VS Code version: Code - OSS 1.72.0 (c4722f1bb292284e0437eb7547808a5788fe6430, 2022-09-02T06:52:06.316Z)
OS version: Linux x64 6.0.1-dirty
Modes:
Sandboxed: No
System Info
Item
Value
CPUs
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz (4 x 3392)
Activity
elahehrashedi commentedon Nov 18, 2022
Thank you for reporting this issue. We were able to repro it in Linux (not windows).
Reuse cmake.environment at init to avoid ENOENT errors (microsoft#2855)
Reuse cmake.environment at init to avoid ENOENT errors (microsoft#2855)
Reuse cmake.environment at init to avoid ENOENT errors (microsoft#2855)
Reuse cmake.environment at init to avoid ENOENT errors (microsoft#2855)
Reuse cmake.environment at init to avoid ENOENT errors (#2855) (#4414)
Reuse cmake.environment at init to avoid ENOENT errors (microsoft#2855)âĶ