I need to exclude directories from the report while using a cmake generated json file with --project because I don't like to run cppcheck on 3rd party dependencies. I tries an approach with the suppression list but in this case the html report is flooded with all the suppression paths. How can I achive a clean and usable report from the cppcheck tool?
Cheers,
frank
Last edit: Frank 2017-10-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think that people usually don't want to see warnings for external files at all. Can it be seen in the compile database that these are external files?
what do you want to exclude specifically.. do you want that cppcheck don't check certain source files at all? Or do you want to avoid warnings in included headers?
ideally if you use a 3rd party library then you create a cfg file for that library. If you frequently use 5-10 functions in that library then you could at least provide configuration for those 5-10 functions. No configuration is needed for functions you do not use. this is usually better than including the headers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi guys,
I need to exclude directories from the report while using a cmake generated json file with --project because I don't like to run cppcheck on 3rd party dependencies. I tries an approach with the suppression list but in this case the html report is flooded with all the suppression paths. How can I achive a clean and usable report from the cppcheck tool?
Cheers,
frank
Last edit: Frank 2017-10-02
I think that people usually don't want to see warnings for external files at all. Can it be seen in the compile database that these are external files?
what do you want to exclude specifically.. do you want that cppcheck don't check certain source files at all? Or do you want to avoid warnings in included headers?
ideally if you use a 3rd party library then you create a cfg file for that library. If you frequently use 5-10 functions in that library then you could at least provide configuration for those 5-10 functions. No configuration is needed for functions you do not use. this is usually better than including the headers.