Skip to content

Fix #14880 add support for Folders in slnx project file and skip non C++ projects#8681

Open
IOBYTE wants to merge 11 commits into
cppcheck-opensource:mainfrom
IOBYTE:main
Open

Fix #14880 add support for Folders in slnx project file and skip non C++ projects#8681
IOBYTE wants to merge 11 commits into
cppcheck-opensource:mainfrom
IOBYTE:main

Conversation

@IOBYTE

@IOBYTE IOBYTE commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@IOBYTE IOBYTE changed the title WIP add support for Folders in slnx project file and skip non C++ projects add support for Folders in slnx project file and skip non C++ projects Jul 2, 2026
@IOBYTE

IOBYTE commented Jul 2, 2026

Copy link
Copy Markdown
Contributor Author

this should be ready to go now

@IOBYTE IOBYTE changed the title add support for Folders in slnx project file and skip non C++ projects Fix #14880 add support for Folders in slnx project file and skip non C++ projects Jul 2, 2026
danmar
danmar previously approved these changes Jul 9, 2026
@danmar

danmar commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Sorry for slow review. I approve this. However there is a conflict in selfcheck.yml. If you fix that then feel free to merge.

@IOBYTE

IOBYTE commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

I think I fixed the conflict but I can't figure out how to make github happy.

These hardcoded file and line numbers are a constant problem.

@danmar

danmar commented Jul 11, 2026

Copy link
Copy Markdown
Collaborator

These hardcoded file and line numbers are a constant problem.

I agree, if we would implement a proper "cppcheck warning hash" similar in spirit to coveritys CID then we could suppress that instead.
Such hash would make our sarif output more proper also.

@danmar

danmar commented Jul 11, 2026

Copy link
Copy Markdown
Collaborator

I agree, if we would implement a proper "cppcheck warning hash" similar in spirit to coveritys CID then we could suppress that instead.

it should be possible to suppress unusedFunction warnings using the symbolName instead.

@danmar

danmar commented Jul 11, 2026

Copy link
Copy Markdown
Collaborator

I made this PR #8714 to make the suppressions more flexible please feel free to review it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants