-
Notifications
You must be signed in to change notification settings - Fork 11
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
Feature request - Support VS Code commands in settings #13
Comments
Yep, that would be nice :) Unfortunately, VS Code does not exposes variableResolver yet (which is weird as a lot of extensions need this thing). |
cmake-tools supports it at least in launch.json, so maybe it is possible with a workaround? |
cmake-tools has its own variables parser under the hood. And so does disasexpl, just not that powerful (yet). I think that current resolver needs to be rewritten, with variableResolver as a good reference. |
It would be pretty sweet to support VS Code commands like:
${command:cmake.buildDirectory}
or${env:VARIABLE}
in the settings as this would add a lot of possibilities and make setup for CMake projects work properly.
The text was updated successfully, but these errors were encountered: