Skip to content
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

${workspaceFolder} is not resolved on VSC start #3658

Closed
ANauzet opened this issue Mar 15, 2024 · 2 comments · Fixed by #3685
Closed

${workspaceFolder} is not resolved on VSC start #3658

ANauzet opened this issue Mar 15, 2024 · 2 comments · Fixed by #3685
Assignees
Labels
bug a bug in the product
Milestone

Comments

@ANauzet
Copy link

ANauzet commented Mar 15, 2024

Brief Issue Summary

I have a workspace with a settings.json with:
"cmake.cmakePath": "${workspaceFolder}\\Tools\\cmake\\bin\\cmake.exe"

When starting VSC, the following error are displayed:

[proc] Executing command: ${workspaceFolder}\Tools\cmake\bin\cmake.exe --version
[proc] The command: ${workspaceFolder}\Tools\cmake\bin\cmake.exe --version failed with error: Error: spawn ${workspaceFolder}\Tools\cmake\bin\cmake.exe ENOENT
[proc] Executing command: ${workspaceFolder}\Tools\cmake\bin\cmake.exe -E capabilities
[proc] The command: ${workspaceFolder}\Tools\cmake\bin\cmake.exe -E capabilities failed with error: Error: spawn ${workspaceFolder}\Tools\cmake\bin\cmake.exe ENOENT

If I replace ${workspaceFolder} by the "real" path, there are no error. But I need to use ${workspaceFolder} so that it work for any coworker using the projet in its own directory

After start, it work but having error displayed on start is confusing, especially for coworker not familiar with CMake

CMake Tools Diagnostics

No response

Debug Log

No response

Additional Information

No response

@gcampbell-msft
Copy link
Collaborator

@ANauzet Thanks for posting this issue! We should be supporting this macro, so this is definitely a bug.

@gcampbell-msft gcampbell-msft added bug a bug in the product and removed triage labels Mar 21, 2024
@gcampbell-msft gcampbell-msft added this to the Backlog milestone Mar 21, 2024
@gcampbell-msft gcampbell-msft moved this from Triage Needed to Pending Prioritization in CMake Tools Mar 21, 2024
@gcampbell-msft gcampbell-msft modified the milestones: Backlog, 1.18 Mar 27, 2024
@gcampbell-msft gcampbell-msft self-assigned this Apr 2, 2024
@gcampbell-msft gcampbell-msft moved this from Pending Prioritization to To Do in CMake Tools Apr 2, 2024
@gcampbell-msft
Copy link
Collaborator

@ANauzet PR opened here #3658

@gcampbell-msft gcampbell-msft moved this from To Do to In Progress in CMake Tools Apr 2, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Completed in CMake Tools Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug a bug in the product
Projects
Status: Completed
Development

Successfully merging a pull request may close this issue.

2 participants