Can`t use custom error parser

Thom Little

2005-04-18 20:56:22 UTC

It took me a while to recall the "lunacy" surrounding this problem ...
forwarding from an old post.
I can't say if any of the links or passwords still work.

Note that steps 2, 3, and 4 are doing what you want.

My guess is that you may be overlooking the name in the list of error
parsers. This one is vivid in my memory for its obscurity.

----------------------------

On Fri, 26 Dec 2003 16:45:41 -0500,
"Thom Little" <***@tlanet.net> wrote:

tlaSolutionExport is now available at
www.tlanet.net/purchase/tlaSolutionExport/evaluation

When prompted for a User Name enter - beta
When prompted for a Password enter - tlaSolutionExport

tlaSolutionExport exports all Solution build errors to CodeWright for
processing.
- Export file is proj.err and is in the same directory as the .sin file
for the build.
- Each error is displayed as Number : Description : Filename

Install tlaSolutionExport ...

1. Install Add-In - Run the application ...
tlaSolutionExportSetup.msi
... to install the Add-In in your copy of Visual Studio .NET 2003. It can
then be controlled using the Add-In Manager.

2. Install Error Parser - Add the following statement to your CodeWright ...
_Init_API_Macro
... macro to install a custom error parser ...
ErrinfoAddRegex( "tlaSolutionExport", "\\3\\1\\2", "^\$([0-9]+)\$ :
(.*) : (.*)$" );
... (An example is provided.)

3. Install optional Calling Macro - Install the macro ...
tlaSolutionExport

4. Reload CodeWright.

5. Enable Error Parser - Select the error parser ...
_ErrorInfoParser tlaSolutionExport
... for your relevant project.

Use tlaSolutionExport...

1. Run the Visual Studio Solution build or rebuild.

2. In CodeWright issue tlaSolutionExport with the directory name for
proj.err (it defaults to the current directory) to load the error file.

3. When the Output window Output pane opens, double-click on any error to
load the corresponding file and position to the line containing the error.

Your feedback would be greatly appreciated.
--
-- Thom Little -- www.tlanet.net -- Thom Little Associates, Ltd.
--

Post by uhansen
Hallo,
i defined a custom error parser (_KeilArm) and tried to use it.
The Regular expression was tested with find and it's correct.
I wonder that the new parser doesn`t appear in the "ErrorParser select
box". If i just write it down, I get the message: "End of parser list
encountered" afer compiling.
I think that the new parser is not used by codewright.
The definition also doesn't appear in any ini-File.
TagSetCmd='${HOME}${WTAGS} -oc -d -t${TAGFILE}.tag
-p${TAGFILE}.ptg',0x8000060
BrowseSetFile='C:\Mapped-D\EW\CW32\tagfile.ptg'
TagSetFile='C:\Mapped-D\EW\CW32\tagfile.tag'
CompilerAddCmdEx='Keil Compiler for
ARM','',1073741824,'',1073741824,'${FTEE} make.bat',144,'${FTEE}
make.bat',0,'${FTEE} make.bat',144,'${FTEE}
make.bat',0,'',2,'',0,'_KeilArm','_KeilArm','_GNUErrorInfo','%x%y.err','%x'
CompilerAddResponse='Keil Compiler for ARM',
CompilerAddCmdEx='$_cw_proj_hash_$','',1073741824,'',0,'${FTEE}
make.bat',176,'${FTEE} make.bat',176,'${FTEE} make.bat',176,'${FTEE}
make.bat',176,'',0,'',0,'_KeilArm','_KeilArm','_KeilArm','d:\projekte\Arm\blinky\proj.err','%x'
CompilerAddResponse='$_cw_proj_hash_$',
CompilerAssign='Keil Compiler for ARM','.c'
By the way what is $_cw_proj_hash_$?
Unfortunately I'm not yet fimilar with CW-API.
Thanks for help.
Uli
--
uhansen
------------------------------------------------------------------------
Posted via http://www.codecomments.com
------------------------------------------------------------------------