Currently CodeChecker keeps track a set of compiler flags which are not or only partially supported by Clang. When this list has to be extended then users need to wait for the next CodeChecker release where the extra flag is handled too.
We were planning the usage of a common CodeChecker config file which could be placed to the analyzed project's directory. Maybe after having this config file this list could be placed there.
It should be highlighted that the filtering is done for the gcc/g++ compiler options.
Compiler option processing and filtering is done differently if the original compiler was clang.
Currently CodeChecker keeps track a set of compiler flags which are not or only partially supported by Clang. When this list has to be extended then users need to wait for the next CodeChecker release where the extra flag is handled too.
We should give the user the ability of extending the list. We should introduce a config file which contains a list of regex like here: https://github.com/Ericsson/codechecker/blob/85db128fee2f17e4c2b0382c8f448347c8c4a4f0/analyzer/codechecker_analyzer/buildlog/log_parser.py#L65
We were planning the usage of a common CodeChecker config file which could be placed to the analyzed project's directory. Maybe after having this config file this list could be placed there.