Comments on: Using PC Lint in Eclipse – no plug-ins required

By: Johan Bezem

Johan Bezem — Thu, 29 Sep 2011 07:12:27 +0000

Sorry for the long response time, I'll try to improve. What options did you provide in step 5? I don't have eclipse running at the moment, but the options/parameters you have to provide in step 5 determine what parameters lint-nt.exe will see. It looks as if there's a potential problem. If you have used my "How to wield PC Lint" document, the options could read something like
loptions.lnt project.lnt temp.lnt -u ${selected_resource_loc}
If that doesn't help, please provide some more details of what you did. HTH, Johan

By: dobromy

dobromy — Fri, 29 Jul 2011 11:59:39 +0000

Good description!

But unfortunately it didn’t help me to integrate PC-Lint into Code-Warrior V10.1 based on Eclipse. I did all the steps described above and it was possible to call lint-nt application as soon as I tried to biuld a project, but no files were passed as argument!

What could be my mistake?

BR.
Peter

By: nietfou

nietfou — Thu, 09 Dec 2010 08:54:04 +0000

I finally found a solution to avoid the Eclipse limitation in specifying options through the Buid(incremental build) text field.

The way I choosed is to define the whole command line in a batch file and to reference this batch file instead of the lint-nt.exe.

By: nietfou

nietfou — Thu, 09 Dec 2010 08:30:47 +0000

I found the reason of the -j option always present. On the behaviour tab, “use parallel build” must be unchecked to remove the -j option.

But now, when this is the build options provided in the Build(Incremental build) text field that are the problem. If using the -os(xxx) option, Eclipse complains because there are options after the ‘)’ character. If using the >xxx syntax to redirect output, error 72: bad option is mentionned. The options (-b loptions.lnt project.lnt temp.lnt files.lnt >lintout.tmp) are not the cause as they don’t make any problem when used when calling lint-nt from the command line.

It seems a lot changed since Ganymede release. Where you not encountering such problems?

By: nietfou

nietfou — Thu, 02 Dec 2010 12:58:58 +0000

Dear Johan,

I tried to apply your hints to use PC-Lint in Eclipse. I’m not using the Ganymede version but the Galileo (In fact Altium Tasking running on Eclipse Galileo). I’m getting a strange behavior in the Build command field. There is always a -j option automatically added to the build command I’m entering. Did you also encounter this behavior with Ganymede? PC-Lint doesn’t support this -j option and stops executing.

Any hint about this issue welcomed!

Best regards.

J-D

By: KolbenJoe

KolbenJoe — Mon, 22 Nov 2010 13:09:58 +0000

Great description!

That’s what I was missing – I always tried fruitlessly with Lint as external tool and additional error parsers.
Now I am able to lint a single file using the string ” -u ${selected_resource_loc}” in the workbench build behaviour.

best regards,

Thorsten