Piping compiler output to a script

[falk.brettschneider at gmx.de]

> Is KDevelop 3.0
> the trunk in CVS
cvs HEAD

> > And the reformatting of gcc errors concerning to templates would just
> mean
> > another additional regular expression there.
> > 
> I'm not sure what you mean here...?
+
> As far as I can understand compiler errors should be sent through
> STLfilt (if the user wants to), before being sent to the Messages
> output. Would that be the correct approach?
KDevelop internally filters the gcc output through several QRegExp's before
the text comes out of the output view. For instance it colours the error
messages red.

I just mean you shouldn't use STLfilt but wrote additional Qt regular
expression for STL gcc-error-messages. Those must be added in
parts/outputviews/makeview.*
But of course you can see how STLfilt works to do the same in our QRegExp.

Anyway it's a good idea to beautify the gcc output ;-)

Ciao
F at lk

> 
> Regards,
> --
> Tarjei

-- 
+++ GMX - Mail, Messaging & more  http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!


-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«