Fix headers and include resolution by specifying compileCommand.json path #1085
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Download the artifacts for this pull request: |
|
@radurentea hi ! Tested: LGTM 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Added compileCommands.json path, this will help getting rid of the squiggly lines in C files for the esp projects after build.
Task: https://jira.espressif.com:8443/browse/VSC-1234
Type of change
Steps to test this pull request
Provide a list of steps to test changes in this PR and required output
The file should display no errors (no squiggly red lines)
How has this been tested?
Created esp projects using all possible options in VS Code Extension on Windows 11 with no issues shown after building the projects.
Test Configuration:
Checklist