Re: [cdt-dev] Error Parser for external compiler. How to?

[Eclipse_Keil <llw2go@xxxxxxxxx>]

Hi Andrew,

i've try the ErrorParser from CDT (I only have CDT 6.0.1). All the option in
Project -> Proporties -> C/C++ Build -> Settings -> Error Parsers are
checked, however nothing happens.

>From where get ErrorParser the input?

Thanks
Mike


Andrew Gvozdev-2 wrote:
> 
> Hello,
> In CDT user forum I suggested to use CDT Regular Expression Error Parser
> which is now part of CDT 6.1. Did you try that?
> 
> Andrew
> 
> On Mon, Nov 9, 2009 at 5:48 PM, Eclipse_Keil <llw2go@xxxxxxxxx> wrote:
> 
>>
>> Hi,
>>
>> In a lot of thread ask poor guys like me about how to add Error Parser to
>> eclipse, i've spend the whole day today looking for the answer for this
>> qustion, failed.
>>
>> Yes, this may seems to be a naiv question for thoes who knows how to do
>> it,
>> but unfortunately not for me. Confused Shocked
>>
>> I used to use CodeWright+Keil UV2 to devolep embedded C software. Now i
>> want
>> to change to Eclipse+Keil. Eclipse is the king of editor, without any
>> question. So i use Eclipse as editor and invoke UV2 to compile the
>> project:
>>
>> Project -> Proporties -> C/C++ Build -> Build Command: MyBuild.bat
>>
>> MyBuild.bat:
>> --------------------------------------------------------
>> c:\keil\uv2\uv2 -b Rcv.Uv2 -o "BUILD.LOG"
>> @echo off
>> FOR %%G in (BUILD.LOG) DO type %%G
>> --------------------------------------------------------
>>
>>
>> In this way i can get the project compiled and the build info showed in
>> console. So far so good.
>>
>> However the logs showed in console is pure text, so i can't jump to the
>> place by double-click.
>>
>> --------------------------------------------------------
>> Build target 'Target 1'
>> compiling Tstopc.c...
>> assembling .\MICRO_A\Tstopc.src...
>> compiling Tstreg.c...
>> assembling .\MICRO_A\Tstreg.src...
>> compiling Scnsync.c...
>> .\SRC\SCN.C(59): error C67: 'scn_T8idx': undefined identifier
>> .\SRC\SCN.C(70): error C67: 'scn_timerReload': undefined identifier
>> .\SRC\SCN.C(71): error C67: 'scn_T8idx': undefined identifier
>> .\SRC\SCN.C(73): error C67: 'scn_searchForOld': undefined identifier
>> .\SRC\SCN.C(78): error C67: 'sy_Sync': undefined identifier
>> .\SRC\SCN.C(78): error C67: 'SY_FIRST': undefined identifier
>> --------------------------------------------------------
>>
>> Then i realize i must use a error parser to let the logs showed in
>> "Problems
>> view". Some nice EclipseR suggest me to use ErrorParser e.g. the one from
>> iSystem. I've install it, but i doesn't work.
>>
>> This is what i understand about ErrorParser: ErrorParser get some text
>> from
>> somewhere, parse it and send the result to "Problem View". Is this
>> correct?
>>
>> What i'm not understand is: From where ErrorParser (e.g.
>> http://www.isystem.si/eclipseUpdate/regExErrorParser/) get the text to
>> parse
>> and who triggers the parser?
>>
>> Thousand of thanks, from me and from lots of new EclipseR like me.
>> --
>> View this message in context:
>> http://old.nabble.com/Error-Parser-for-external-compiler.-How-to--tp26215807p26215807.html
>> Sent from the Eclipse CDT - Development mailing list archive at
>> Nabble.com.
>>
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> 
> 

-- 
View this message in context: http://old.nabble.com/Error-Parser-for-external-compiler.-How-to--tp26215807p26285775.html
Sent from the Eclipse CDT - Development mailing list archive at Nabble.com.