Hi Tom!

If you need to access the parser then we need to export it. If you are planning 
to
do a merge request of your code, please just include it their or tell me and 
I'll do
so in a separate commit.

The best approach to avoid duplicating the functionality is most likely adding a
custom parser of your own that redirects part of or all of its input received 
via
stdout to the stderr-receiver of the gcc parser. The tricky part is to figure 
out which
lines need to be passed on to GCC. I do not want the GccParser to just munch 
through
all of the processes stdout-output as the parser is rather fragile:-(.

Could that work for you?

Best Regards,
Tobias Hunger
Software Engineer
Nokia, Qt Development Frameworks

Nokia gate5 GmbH
Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany
Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B
Umsatzsteueridentifikationsnummer: DE 812 845 193
Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori
________________________________________
Von: [email protected] 
[[email protected]]" im Auftrag von 
"ext Tom Deblauwe [[email protected]]
Gesendet: Dienstag, 6. September 2011 11:49
Bis: [email protected]
Betreff: [Qt-creator] output parsers

Hello,

I am porting my projectmanagement plugin to read codeblocks workspace
files to 2.3. It was compiled for 2.1. For parsing the compile output of
gcc, I had to make a workaround because codeblocks prints the output of
the compilation process to stdout and not to stderr so the gcc parser
was not processing anything. I could do this by making my own
outputparser that creates the gcc one and sends my stdout to the stderr
function of the gcc parser. So I created the gcc parser by making a gcc
toolchain and then asking it's output parser.

So this trick does not work anymore with 2.3. Also, the GccParser class
is not exported as public, that's why I was using that trick with the
toolchain. Any suggestions how I could re-use the gcc parser? I could
copy it, but don't like to do this of course.

Thanks,
Best regards,
Tom,

_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt-creator

Reply via email to