There are great Cppcheck plugins for Visual Studio and QTCreator.
Both these provide good in line results.
Both these have 1 config for all projects. You can only configure Cppcheck generally.
This is not ideal when working on diffrent projects with different standards.
Clang-tidy and Clang-format have a good approach for this, where both these tools look for a config file.
Is this also possible with Cppcheck? This would be a great feature!
For example: cppcheck --search-config-file.
This would then allow Cppcheck to search for a config file in the projects and go upwards from there.
Different projects then have different config files, but the plugin only needs to be configured once to use --search-config-file for all projects.
Regards,
Emiel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
There are great Cppcheck plugins for Visual Studio and QTCreator.
Both these provide good in line results.
Both these have 1 config for all projects. You can only configure Cppcheck generally.
This is not ideal when working on diffrent projects with different standards.
Clang-tidy and Clang-format have a good approach for this, where both these tools look for a config file.
Is this also possible with Cppcheck? This would be a great feature!
For example: cppcheck --search-config-file.
This would then allow Cppcheck to search for a config file in the projects and go upwards from there.
Different projects then have different config files, but the plugin only needs to be configured once to use --search-config-file for all projects.
Regards,
Emiel