🐛 Don't add compileCommands to c_cpp_properties #215
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The VSCode C/C++ extension no longer likes the compile_commands we generate for clangd, probably because we aren't actually compiling for clang. We can either generate a separate compile_commands for the VSCode extension, or just remove the compileCommands option from the c_cpp_properties.json we generate. The second option is simpler, since the first would require changes in the CLI (to generate a separate compile_commands for VSCode) and Kernel (to update the gitignore) as well.