Piping compiler output to a script

[Tarjei Knapstad]

On Fri, 2003-03-07 at 10:16, falk.brettschneider at gmx.de wrote:
> Hi,
> 
> > Maybe a bit off topic but anyhow:
> > 
> > I just had a look at STLFilt today
> > (http://www.bdsoft.com/tools/stlfilt.html) which is a Perl script that
> > greatly simplifies the sometimes insane output from gcc when template
> > stuff goes wrong, and I thought I'd make a stab at integrating it into
> > my KDevelop project.
> > 
> > It seems to me that what I basically have to do is parse the compiler
> > output to a Perl script (the perl script needs a few command line
> > options as well).
> > 
> > Does anyone know how I could possibly do this by modifying the
> > configure/automake stuff in my KDevelop project? (or possibly directly
> > in KDevelop?)
> > 
> > I'm using 2.1.4 by the way. It would be a great feature if this is/will
> > be possible in KDevelop 3 (i.e. piping compiler output to whatever
> > script/file), as it could also be used to make build logs and the like.
> 
> Why not adding the functionality of writing the compiler output to a logfile
> to parts/outputviews/makeview.h/cpp?
> 
That is of course the best solution for KDevelop 3.0, but I was hoping
for a quick hack to just add it directly in the makefile at first.

I'll have a look at the makeview code when time permits. Is KDevelop 3.0
the trunk in CVS or a branch? (which tag in the latter case?)

> 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...? If you mean doing the error message
reformatting directly in KDevelop, STLfilt is a rather lengthy piece of
Perl so adding that is IMHO a bad idea (and a maintenance hell). I'd
rather leave STLfilt to the STLfilt guys, and integrate the
functionality into KDevelop.

I'm not very into Gideon at the moment, but an STLfilt plugin is
probably in place (the perl script has a lot of configurable parameters
that would be nice to have available through the KDevelop GUI).

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?

Regards,
--
Tarjei



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