View previous topic :: View next topic |
Author |
Message |
Todd Turner Guest
|
CCS with CodeWright |
Posted: Tue Oct 16, 2001 3:41 pm |
|
|
Hello everyone,
Has anyone successfully integrated CCS with codewright? I am looking to have errors parsed by codewright and easy jump to error by clicking on the error in the output window.
tia
todd
___________________________
This message was ported from CCS's old forum
Original Post ID: 697 |
|
|
Richard Katezansky Guest
|
Re: CCS with CodeWright |
Posted: Tue Oct 16, 2001 9:43 pm |
|
|
:=Hello everyone,
:=
:=Has anyone successfully integrated CCS with codewright? I am looking to have errors parsed by codewright and easy jump to error by clicking on the error in the output window.
:=
:=tia
:=
:=todd
Hi;
Setup your Codewrite project.
Under Project Properties, Tools:
For Category: Compile:
In the Compile Box:
c:\Program Files\picc\ccsc \%b\%e (or whereever your CCS directory is).
Select: "No command shell" in the Command options window
Under Project Properties, Errors:
Error Filename: \%b.err
Error Parser 1: _MPAsmErrorInfo
Hit Alt+F10 and your current file will compile and the error
file will be parsed and displayed in the output window.
Hope this helps.
___________________________
This message was ported from CCS's old forum
Original Post ID: 703 |
|
|
Todd Turner Guest
|
Re: CCS with CodeWright |
Posted: Wed Oct 17, 2001 11:32 am |
|
|
This definitely helps!
thanks
___________________________
This message was ported from CCS's old forum
Original Post ID: 711 |
|
|
geortiz
Joined: 14 May 2005 Posts: 1
|
Re: CCS with CodeWright |
Posted: Sat May 14, 2005 10:37 pm |
|
|
Richard Katezansky wrote: | :=Hello everyone,
:=
:=Has anyone successfully integrated CCS with codewright? I am looking to have errors parsed by codewright and easy jump to error by clicking on the error in the output window.
:=
:=tia
:=
:=todd
Hi;
Setup your Codewrite project.
Under Project Properties, Tools:
For Category: Compile:
In the Compile Box:
c:\Program Files\picc\ccsc \%b\%e (or whereever your CCS directory is).
Select: "No command shell" in the Command options window
Under Project Properties, Errors:
Error Filename: \%b.err
Error Parser 1: _MPAsmErrorInfo
Hit Alt+F10 and your current file will compile and the error
file will be parsed and displayed in the output window.
Hope this helps.
___________________________
This message was ported from CCS's old forum
Original Post ID: 703 |
no me funciono, me entrega un error "duplicate filename on command line "esclavo.c" and ">""
y el error parser "_MPAsmErrorInfo" tampoco esta en la lista. |
|
|
bfemmel
Joined: 18 Jul 2004 Posts: 40 Location: San Carlos, CA.
|
Error Parser |
Posted: Sun May 15, 2005 1:13 am |
|
|
Richard,
You need to build a custom Error Parser for the output from the CCS compiler. I used the following line built using the "regular" search syntax from Codewright. The instructions for this are in the CodeWright help files. You'll find all this under Project ==>Properties==>Errors==>Custom Error Parser
Code: | ^\*\*\* (error|fatal error|warning|syntax error) [0-9]+ "(.+)" Line([0-9]+)\(.+: (.+)$ |
Looking at the line above you can see that there are four grups, each group being a bunch of stuff in parentheses. The second group has the file name, the third has the line number and the forth has the error message. So fill in those numbers in the box on the Errors dialog box. I am pretty sure this works. I had it working before I hosed it over by copying over my codewright project file. If I get it working again I will let you know what else needs to change.
This will cause a jump to the correct line in the correct file once you point it at the right file for errors in the setup.
- Bruce |
|
|
bfemmel
Joined: 18 Jul 2004 Posts: 40 Location: San Carlos, CA.
|
Error Parser |
Posted: Sun May 15, 2005 1:36 am |
|
|
Ok, I got it working again. The line above has one error in it. Put a space between "Line" and the next '(' since there is a space there in the error message that CCS produces.
Have fun,
Bruce |
|
|
|