I am a little surprised to get way less (in a project of ~1000000 loc 3000 issues instead of 17000) also severe findings when adding include paths to the cppcheck-call. My expectation would be, it would be more as cppcheck knows a lot more about the used functions and librarys.
I am aware there might be a lot more combinations of defines but I tried it with --force as well.
Are there chances there's a bug somewhere?
Best regards,
Christoph
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is hard to say why this happened. What kind of includes did you add? System headers or project headers? You are not supposed to include Qt, posix, windows headers, stdio.h iostream and stuff like that.
Are there chances there's a bug somewhere?
I guess so.
If you use --enable=all do you get any internalAstError, syntaxError, unknownMacro, cppcheckError,cppcheckLimit, instantiationError messages?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for the delay, I had some holiday in the meantime....
Currently I am adding the whole include path which is covering the compiler includes as well (MSVC 9 or 19).
Let my try to create a minimalistic sample showing the difference. I'll come back to you soon...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello everybody,
I am a little surprised to get way less (in a project of ~1000000 loc 3000 issues instead of 17000) also severe findings when adding include paths to the cppcheck-call. My expectation would be, it would be more as cppcheck knows a lot more about the used functions and librarys.
I am aware there might be a lot more combinations of defines but I tried it with --force as well.
Are there chances there's a bug somewhere?
Best regards,
Christoph
It is hard to say why this happened. What kind of includes did you add? System headers or project headers? You are not supposed to include Qt, posix, windows headers, stdio.h iostream and stuff like that.
I guess so.
If you use
--enable=all
do you get anyinternalAstError
,syntaxError
,unknownMacro
,cppcheckError
,cppcheckLimit
,instantiationError
messages?Sorry for the delay, I had some holiday in the meantime....
Currently I am adding the whole include path which is covering the compiler includes as well (MSVC 9 or 19).
Let my try to create a minimalistic sample showing the difference. I'll come back to you soon...