Work around C/CPP limitation of ${workspaceFolder} not being substituted - Githubissues

betwo / vscode-catkin-tools

VS Code extension for catkin_tools support

https://marketplace.visualstudio.com/items?itemName=betwo.b2-catkin-tools

MIT License

24 stars 7 forks source link

Work around C/CPP limitation of ${workspaceFolder} not being substituted #4

Closed betwo closed 5 years ago

betwo commented 5 years ago

Currently, as of version 0.22.0, the C/C++ extension does not replace ${workspaceFolder} or the legacy ${workspaceRoot} in the configurations.compileCommands configuration, which causes different kinds of problems:

Detection of changes in compile_commands.json
Switching between source and header

Ideas for workarounds:

Replace the absolute paths in compile_commands.json with the variable ${workspaceFolder}
Warn the user if configurations.compileCommands is not resolved