Re: [cdt-dev] Running external tools with error parsing "org.eclipse.cd

[James Blackburn <jamesblackburn@xxxxxxxxx>]

Alternatively you can instantiate and use the ErrorParserManager
directly.  If you're not running your tools as part of a build then
this may be the way to go (it'll be faster as you don't lock the
workspace, perform unnecessary refreshes etc.). It's relatively
straightforward to attach and EPM to any outputstream:

			String[] errorParsers = "my_error_parsers";
			ErrorParserManager epm = new ErrorParserManager(currentProject,
defaultDirectory, MyMarkerGenerator, errorParsers);
			epm.setOutputStream(outputStream);

See ManagedBuild's CommonBuilder.java / the ErrorParser tests for more.

James


2009/7/8 Achim Bursian <abu.aud@xxxxxxxxxxx>:
> Andrew Gvozdev wrote on 2009-07-08 23:56:
>>
>> If your parsers conflict with each other that may be problematic - as they
>> do use the same set of parsers. But if you use your own UI I guess you could
>> set the list of parsers programmatically every time for a configuration.
>
> You mean determining the active configuration (what's the API?), saving its
> state, then activating a special error parser in the configuration,
> launching the make target, and then reverting the configuration to its
> previous state?
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>