[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Scanner configuration correctness for CDT 3.0 featu re specs document available
|
> -----Original Message-----
> From: cdt-dev-admin@xxxxxxxxxxx
> [mailto:cdt-dev-admin@xxxxxxxxxxx] On Behalf Of Vladimir Hirsl
> Sent: November 8, 2004 3:43 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: Re: [cdt-dev] Scanner configuration correctness for
> CDT 3.0 feature specs document available
>
>
> Ed,
> You are right in your analysis.
> There were three factors (at least that I know of) that were
> slowing down the processing of output and error streams:
> 1. Extra layer of pipes through use of PipedOutputStream and
> PipedInputStream objects in CommandLauncher.java. This has
> already been addressed.
> 2. Error parsers that parse the build output for compilation
> and other errors.
> 3. SC console parser that parses for SC affecting compiler options.
Around here somewhere, gathering dust no doubt, is a plugin that
I wrote that added an "C/C++ Compile Error Importer" to the CDT.
This allowed you to take your builds and pipe the output to a
file, achieving a much higher throughput. Then later you could do
an "import" of the error file to get all of the error markers etc.
It needs to be re-visited, but if anyone is interested, I'm happy
to make it available.
Coupling this file import as a build action that can occur on its
own might be interesting.
Thomas
