Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] [Build selected File] Compiler Errors are not shown in Problems View

Arrghh...

I missed to reimport the CDT sources in my Eclipse SDK.

I was looking in 6.0.0.200909110608.

In 6.0.0.201004122116 the mentioned call has been changed to a DescriptionBuilder.
And it doesn't look like a stream problem any more.

But the problem still exist. The problem markers are not created with our toolchain when the command "Build selected File(s)" is executed.

Cheers,
Harald

> -----Urspr√ľngliche Nachricht-----
> Von: Kaestel-Baumgartner Harald (DC-IA/EDF2)
> Gesendet: Freitag, 15. Oktober 2010 17:10
> An: 'CDT General developers list.'
> Betreff: [cdt-dev] [Build selected File] Compiler Errors are
> not shown in Problems View
>
> Hi,
>
> I've added a editor action with key binding to compile the
> File in the current editor.
>
>
> org.eclipse.cdt.managedbuilder.internal.core.GeneratedMakefile
> Builder.invokeInternalBuilder
> was my blue print.
>
> BTW I've seen, that following call in the blue print is wrong
> (I think):
>   int status = stepBuilder.build( consoleOutStream, epmOutputStream,
>                    new SubProgressMonitor(monitor, 1,
> SubProgressMonitor.PREPEND_MAIN_LABEL_TO_SUBTASK));
>
> epmOutputStream is the stream of the ErrorParserManager an
> consoleOutStream the stream of the console.
>
> With our toolchain we've the problem, that for the compile
> errors no problem markers are generated, when the command
> "Build selected File(s)" is executed. Now I think they are
> not on the err stream and thus are not scanned by the
> ErrorParserManager. In my editor I've changed the call to
>   int status = stepBuilder.build( epmOutputStream, epmOutputStream,
>                    new SubProgressMonitor(monitor, 1,
> SubProgressMonitor.PREPEND_MAIN_LABEL_TO_SUBTASK));
> and the problem markers are generated.
>
> Is it a bug or a feature?
>
> The code snippet is from CDT 6.0.2 (what we use). CDT 7.1
> doesn't generate problem markers, too.
>
> Cheers,
> Harald
>
>


Back to the top