#5 Problems configuring CppChecker for PC-lint

[Martin Stolpe]

Hello,

I wanted to use CppChecker together with PC-lint. My problem is that I don't see any error markers in the editor. I've tried the Indigo and Kepler releases of Eclipse. The dialogs for configuring CppChecker are a little bit different between the two versions (see attached screenshots, especially Indigo_CppChecker_Settings_PC-Lint_Settings.png and Keppler_CppChecker_Settings_PC-Lint_Settings.png).
The source code is targeted for a MSP430 microcontroller and the compiler we use is the one from the IAR Embedded Workbench.
The installed features for CppChecker are the "CppChecker Feature" and the "CppChecker PcLint Parser".

Regards
Martin

[Martin Stolpe]

Screenshot with Eclipse settings

[Martin Stolpe]

PC-lint configuration files

[Michael Schulte]

Hello,

Configuring PC-Lint to get it running right is probably the hardest part - and sorry, but this is not done automatically - or at least only some output features are set by the plug-in. The rest has to be done by the developer.

If you have problems, first try to activate the log output: Trace-Level: Info, Trace Parser, Write to Console. This should give you some idea what went wrong.

Basically it should be possible to run PC-Lint with the same settings in the plug-in as you would use on a command line. It gets admittedly a bit tricky to get the right command line parameters, when PC-Lint is called by an external build tool. One hack would be to copy the pc-lint.exe safely away and replace it by an (self-built) executable that logs its call parameters to some log file and call your build tool. Afterwards restore pc-lint.exe and use the parameters as provided by the log-file.

I haven't checked if the plug-in still runs on Kepler - it did run however on Juno.

Sorry, if I can't help any further.

Cheers
Michael