[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.tools.cdt] Re: PC-Lint Error Parser in Eclipse

Hi Ron,

Thanks for your advice. That certainly does help! I will get right onto it.

Thanks,

RG

Ron Bermejo wrote:

RG wrote:

Hi all,

I am looking for advice on using PC-Lint within the Eclipse platform. The C-based project that I am part of, uses a custom perl script to build the project, there is also a lint option that does a PC-Lint analysis on the Source Code. Within Eclipse, I am using the perl script as an External builder, I also have a lint Make Target that runs the build script with the lint option. The output from lint is output into the console, it would be nice if the console output could be used to generate data to fill in the Problems & Tasks View/Tabs in Eclipse.

I have searched around and cannot find any Plug-in that integrates PC-Lint with Eclipse so I think I would have to create my own. Unfortunately, I have only very recently started using Eclipse and frankly do not know where to start. I know that I have to create an Error Parser to evaluate the PC-Lint output in console and then generate the right data for the Problems View.

Can anyone offer me advice on what I need to do, or are there any examples of something similar, so that I can reverse engineer it?

My spec is as follows:
version 3.3 of the Eclipse Platform.
version 4.0.1 CDT.
compiler is GCC 3.4
The project is all in C
PC-Lint version is 8.0
Development machine is WindowsXP Pro

Many Thanks in advance for any help you can give me.

Hello RG,

A PC-Lint error parser for CDT would be useful indeed. :-)

I think what you are looking for is this extension point:
org.eclipse.cdt.core.ErrorParser

You simply need to create your own plug-in that contributes to this extension point. Then, you will need to create a class that extends IErrorParser.

For reference I suggest you install the CDT SDK and do a plug-in search for all references to the extension point org.eclipse.cdt.core.ErrorParser. (No need to reverse engineer! :-))

HTH!
Ron