GCC output parsing
aleixpol at kde.org
Wed Mar 24 20:19:52 UTC 2010
On Wed, Mar 24, 2010 at 8:50 PM, George Syron <mr.syron at googlemail.com>wrote:
> 2010/3/24 Jérémie Dubois-Lacoste <jeremie.dl at gmail.com>
>> I am a user of Kdevelop since 4 years, in love with this IDE.
>> So this message could not start without a huge thanks to all
>> Likely, I will submit a proposal for the google summer of code
>> this next days. My proposal should not concern Kdevelop
>> but the GNU compiler GCC. I am interested in implementing an option
>> to allow XML output instead of natural language to print any kind
>> of warning\errors.
>> There is an existing thread that reports a bug in gcc and speaks
>> about that:
>> The main idea of printing
>> XML output would be to make the parsing by an IDE easier.
>> One advantage of using a machine readable format like XML
>> would be also to allow gcc to output more information.
>> As mentioned in the thread, this could be much more interesting
>> if driven together with some requirement from IDE developers.
>> So, before asking which kind of information could be usefull
>> for an IDE, and how it should be structured, the main question is:
>> Does any of you think it could be of any interest from
>> the IDE point of view (that is, the user using gcc through an IDE...)?
>> And of course, in the particular case of Kdevelop.
> I'm not an IDE developer, but you're mentioning an idea I had a few days
> ago. I think it would be great to do such an output, because there could be
> some useful additional information added to the errors/warnings/etc. (i.e.
> cross references to other lines of code that could have produced that
> specific output). But I even thougt about a "generalized output"; that means
> a proposal for standard code table of error codes, warning codes, etc. that
> a compiler could produce so that an IDE can parse the compiler output of
> _any_ compiler, so that an IDE would become more independent of a specific
> I personally think that this is more like a standard proposal than an IDE
> Kind regards, Syron
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
I think it's really important to have such features available in the
development stack tools. It makes it much easier to integrate applications
into IDE's, so that's great.
If you apply for that it would be great if you came up with something that
is really useful. Right now it's working pretty well with the system we have
in kdevelop (although it could be improved, of course). So you will have a
good application if you can find a good added value to the current state.
Here you can check what such code looks like right now:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel