RE: [cdt-dev] Error parser extension

[djlynott@xxxxxxxxxxxxxxxxxxx]

Mikhail,

After some investigating I discovered
that the ones that worked had the same class name as the ID. When I changed
this, it worked great!

Thanks!
-- Dave

"Sennikovsky, Mikhail" <mikhail.sennikovsky@xxxxxxxxx>
Sent by: cdt-dev-bounces@xxxxxxxxxxx

11/14/2007 02:55 AM

Please respond to
"CDT General developers list." <cdt-dev@xxxxxxxxxxx>

To	"CDT General developers list." <cdt-dev@xxxxxxxxxxx>
cc
Subject	RE: [cdt-dev] Error parser extension

Hi Dave,
 
Specifying error parser in
the tool definition via the “tool#errorParsers” attribute should work.
In case it does not work for you, could you provide a sample tool/tool-chain
definition illustrating the problem?
 
Mikhail

---

From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of djlynott@xxxxxxxxxxxxxxxxxxx
Sent: Tuesday, November 13, 2007 7:09 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Error parser extension
 

Where is the proper point to declare an error parser within the toolchain
so that it becomes automatically checked when a new project is created.
I have specified it within the configuration, the base compiler definition,
derived compiler definition and within the compiler definition for each
project type? While it appears in the list of available parsers, it is
not selected. If selected, it works?

Thanks, 
-- Dave

--------------------------------------------------------------------
Closed Joint Stock Company Intel A/O
Registered legal address: 125252, Moscow, Russian Federation,
Chapayevsky Per, 14.

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev