| different error parser in standard make [message #157931] |
Mon, 14 November 2005 10:33  |
Eclipse User |
|
|
|
Originally posted by: henrik.lindstrom.ericsson.com
I am trying to implement a remote make using a standard make project.
The build is working but I want CDT to parse the result.
How can I add different error parsers to a standard make project? I lack
the possibility to edit the error parser list in the project settings
(both for managed build and standard make projects).
Is it only possible by defining a new managed build system? However I do
not want to specify all the tool-chain since I am just needing the
'standard make' part for my remote make. I tried to skip the
tool/configuration parts of the extension but then the project settings
dialog will get exceptions when I try to use it (since the compiler etc
are missing).
Regards,
Henrik
|
|
|
|
|
| Re: different error parser in standard make [message #158181 is a reply to message #158087] |
Wed, 16 November 2005 14:27  |
| Eclipse User |
|
|
|
Originally posted by: eclipse.dharty.com
First, is your error parser selected? You mention that it is listed,
but you never said if you selected it.
Second, have you tried running it from the plugin debugger? Put a
breakpoint at the entry point of your parser, launch the debugger, open
up a project in the "Debug" eclipse, ensure that the error parser is
selected, and then try to build some code with a known error.
If your breakpoint is never hit, you have a problem, but if it your
parser is showing up in the parser list, it should be getting called.
D
Henrik L wrote:
> "Henrik L" <henrik.lindstrom@ericsson.com> wrote in message
> news:1a6e1195e58fa7d91286d0ed90f94f0d$1@www.eclipse.org...
>
>>I am trying to implement a remote make using a standard make project.
>>The build is working but I want CDT to parse the result.
>>
>>How can I add different error parsers to a standard make project? I lack
>>the possibility to edit the error parser list in the project settings
>>(both for managed build and standard make projects).
>>
>>Is it only possible by defining a new managed build system? However I do
>>not want to specify all the tool-chain since I am just needing the
>>'standard make' part for my remote make. I tried to skip the
>>tool/configuration parts of the extension but then the project settings
>>dialog will get exceptions when I try to use it (since the compiler etc
>>are missing).
>>
>>Regards,
>>Henrik
>>
>
>
>
> "Henrik L" <henrik.lindstrom@ericsson.com> wrote in message
> news:7c3a40f368eda16d902cc21ce552318d$1@www.eclipse.org...
>
>>Found the answer myself. Any Error Parser is automatically available in
>>the error parser list. I did not see that anywhere in documentation but
>>now I tested and my parser is listed under preferences.
>>Thanks anyway...
>>
>
>
> No, I cannot get CDT to run my new error parser. Seems like it is not loaded
> at all. I've added tracing but it is never called.
> The error parser, a clearmake variant of the make parser, is listed in the
> Error Parser tab for standard C/C++ make project, but when I perform a built
> it does not get called.
>
> Any ideas? Could this be a bug?
> /Henrik
>
>
|
|
|
| Re: different error parser in standard make [message #158707 is a reply to message #158181] |
Tue, 22 November 2005 05:13 |
| Eclipse User |
|
|
|
Originally posted by: henrik.lindstrom.ericsson.com
David H wrote:
> First, is your error parser selected? You mention that it is listed,
> but you never said if you selected it.
> Second, have you tried running it from the plugin debugger? Put a
> breakpoint at the entry point of your parser, launch the debugger, open
> up a project in the "Debug" eclipse, ensure that the error parser is
> selected, and then try to build some code with a known error.
> If your breakpoint is never hit, you have a problem, but if it your
> parser is showing up in the parser list, it should be getting called.
> D
Yes, I made those steps. I set a breakpoint as well and run the debugger.
Made a new project and selected the parser (replaced the make error parser
and put it first in the error parser list as well).
But while building code it never enter my plugin. I might add the I use
this for a "remote build" which I perform like this using a standard make
project.
- Replace 'make' command with "rsh [HOST]-l [USER]
/usr/atria/bin/cleartool setview -exec 'cd [SRCPATH];make' [VIEW]"
It is in its beginning state so for now I have settled with hardcoded
arguments, but will change to at least variables (the [XXX] parts). Or
perhaps make some extension to the clearcase plugin since source is in
clearcase on the remote build machine as well.
The build is working (I see output in eclipse console). However clearmake
report any error beginning with "clearmake:" instead of "make:" as the
default make error parser expects.
The default linker error parser is reporting a few errors so integration
between my remote make command and CDT seems to work, just my own parser
is not run.
Henrik
|
|
|
Powered by
FUDForum. Page generated in 0.04440 seconds
Home