{{ message }}
Fix #14854 (import project: Handle forced include files from compilation database projects)#8641
Open
JonnyPtn wants to merge 1 commit into
Open
Fix #14854 (import project: Handle forced include files from compilation database projects)#8641JonnyPtn wants to merge 1 commit into
JonnyPtn wants to merge 1 commit into
Conversation
Sorry, something went wrong.
danmar
reviewed
Jun 17, 2026
danmar
left a comment
danmar
left a comment
Collaborator
There was a problem hiding this comment.
lgtm.
I created https://trac.cppcheck.net/ticket/14854
Can you please change the PR title to:
Fix #14854 (import project: Handle forced include files from compilation database projects)
Sorry, something went wrong.
Collaborator
|
after the merge.. we should make sure your name is in the AUTHORS file. Which name do you want that we write there? |
Sorry, something went wrong.
JonnyPtn
changed the title
Author
|
Thanks - Updated the title, and you can use "Jonny Paton" for my name |
Sorry, something went wrong.
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
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.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.
Sorry, I don't have access to the bug tracker so haven't been able to log an issue, but hoping it's simple enough
The problem is that if a project uses forced includes cppcheck does not process these when running via a compilation database which can cause errors.
I appreciate it's possible to workaround using cppchecks
--includeargument, but that means maintaining the force includes in multiple places, and can easily get out of sync with the actual project setup. There may also be file or config specific settingsThis change parses those arguments from the project and respects them, with an accompanying test