As you all probably know CppCheck is static code analyzer tool for C and C++. KDevelop has a plugin that provides a front-end for it, and the plugin is called kdev-cppcheck.
The good news is I’ve updated it’s GUI and now it uses the KDevelop Problem Checker Framework.
In the past it used to have it’s own toolview, where it showed issues in different formats (flat issue list, grouped by files, grouped by issue severity), based on the settings set in a KCM module.
Here’s a screenshot showing and example of this
What I’ve done is break up that KCM module, and create a per project settings window, and a general global settings window. The global settings window allows you to set the location of the cppcheck tool
The per project settings window allows one to set the rest: parameters, and what should be checked
Also the results area now shown in the problems toolview, just like problems found by the background parser, in it’s own tab.
Here’s a video showing the workflow