[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: AW: AW: [cdt-dev] problem to add an error parser to a toolchain
|
>
> Hi,
>
> >
> > Ok, try with the Standard Make project, and enable
> > your NewErrorParser in the Property of the project(or with
> > the wizard during creation). It looks like your NewErrorParser
> > was not register in the ErrorParserManager by the builder.
> > By default, your new parser is probably disable.
> >
>
> I tried it with a new standard project now. Within this project, I =
> enabled the parsers 'GCCErrorParser', 'IARErrorParser' and =
> 'NewErrorParser'.
>
> >From the ErrorParserManager the constructor 'ErrorParserManager(IProject =
> project, IPath workingDirectory, IMarkerGenerator markerGenerator, =
> String[] parsersIDs)' was called, wich builds the list with the error =
> parsers. The attribute 'value' of the entries of the 'GCCErrorParser' =
> and the 'IARErrorParser' is shown as 'IErrorParser[1]', the attribute =
> 'value' of the NewErrorParser is shown as 'IErrorParser[0]'.
>
> >
> > This should rule out an error in the ErrorParserManager class.
> >
>
> Maybe. Can you give me an hint, how I can locate the error?
>
We have to make sure that the Builders when instanciating the ErrorParserManager
pass the right parsersIds.
And it looks like, at least for the standard make ... it is.
But it does not look like it was for the managed builder(If I read your email correctly).
> >
> > Maybe a PR to track this down ?
> >
>
> Please, what is a 'PR'?=20
>
Bugzilla Problem Report.
https://bugs.eclipse.org/bugs/
The component of the bug report should be CDT.
For what is worth, I've try to reproduce the behaviour and both
the Standard Make builder and the Managed Builder pass the right parsers.
So it looks like it is fix in the head.
