Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] Generic Error parser and build discussion

I posted the initial version of Generic or Regex Error Parser in bug 109139. It led to quite a few changes listed in comment #10.

I think that this patch might be also interesting from build/project model angle as far as an idea to store elements of build model on workspace level as user-defined "extensions", with initial implementation for error parsers. I think that it may be reasonable to keep common elements of the project model on workspace level - for many workflows - and make .cproject leaner. Considering that we already have such requests, see bug 244874 or bug 248764.


On Mon, Jun 29, 2009 at 9:59 AM, Andrew Gvozdev <> wrote:

I've been working on generic RegexErrorParser which I think would make nice addition to CDT. You can take a look at the screenshots in bug 109139. I got it working from extension point where you could define regular expressions to the project properties UI.

And now I am facing the project model and persistence. The property page (Error Parsers tab) suggests that the settings need to be per project. Can somebody give me any pointers where in the persistence layer I can inject that? Or even better some good example to emulate? Is CConfigurationSpecSettings an appropriate place to plant?


---------- Forwarded message ----------
From: <bugzilla-daemon@xxxxxxxxxxx>
Date: Sun, Jun 28, 2009 at 11:12 AM
Subject: [Bug 109139] Generic Error parser
Product/Component: CDT / cdt-core

James Blackburn <jamesblackburn+eclipse@xxxxxxxxx> changed:

          What    |Removed                     |Added
                CC|                            |jamesblackburn+eclipse@gmail
                  |                            |.com

--- Comment #4 from James Blackburn <jamesblackburn+eclipse@xxxxxxxxx>  2009-06-28 11:10:02 -0400 ---
(In reply to comment #2)
> Created an attachment (id=140268)
 --> ( [details]
> Suggested RegexErrorParser properties screen
> ...
> Here is an example of suggested ErrorParsers properties tab attached. Any
> feedback is welcome.

That looks really neat :). Giving the user more control over this would be
good. Being able to add parsing output for new tools without having to pull out
the PDE / extend the product is bound to help savvy and less-savvy users alike!

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Back to the top