fix: FILE_PATTERN needs to match cpp, cc before c and mm before m#318
Merged
Conversation
This was referenced Sep 4, 2025
Member
|
Thanks! |
Contributor
|
Has this been reverted? Its disappeared from the main branch. |
lionel-
pushed a commit
that referenced
this pull request
Sep 23, 2025
Member
|
Not sure what happened! I just restored, thanks for the heads up |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
When extracting files names from build commands (to generate
compile_commands.json), this file pattern causes"-c file.cpp"to become the name"file.c", because ".c" matches before ".cpp".This will then use a C compiler instead of a C++ compiler, which gives very weird error messages like
<string>not found