I was surprised to learn recently
that the CDT Error Parser
functionality is not used in the
same manner by the Standard
Make and Managed Make build
systems. From what I can tell:
o Standard
Make:
- Allows the user to
set the default for error parsers to be
used and
in what order in the Window -> Preferences -> C/C++
-> New
Make Projects -> Error Parsers tab.
- When a new Standard
Make project is created, allows the user
to modify
the default settings for the new project using the
same
UI.
- Allows the user to
change the settings for the project in the
project
Properties using the same UI.
- During a build,
uses the project settings to determine which
error
parsers to invoke and in what order.
o Managed
Make:
- Doesn't do any of
the above.
- During a build,
uses all error parsers and I don't think there
is any
way to control the order.
I sent mail to Sean a couple of
days ago asking if he was in favor
of me investigating adding the
error parser functionality to the
Managed Make build system, and he
said OK. Having investigated
further, I've decided that the
Managed Make support should be
implemented somewhat
differently.
The per-project support should be
the same - that is, it can be set
during project creation and
changed by editing the project properties.
The difference would be in the
project default. It
seems to me to be more appropriate
for each "target" (or "tool
chain") being defined for the
Managed Make build system to specify
the default list and order of the
error parsers needed by the
"tool chain". This could be
specified by each "tool chain" in the
plugin.xml file where the
information for the "tool chain" is
provided (for example, the "binary
parser" and the command line
options.
Comments?
Leo Treggiari
Intel Corp.
