Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Error Parser for external compiler. How to?

Thanks Paolo,

i'm now happy with CDT 6.1, but i think your reply must be helpful for many
others.


Paolo Nenna wrote:
> 
> Hi Mike,
> I have followed step by step the instruction on the link that I sent you.
> After this you need to write your own regex expression. For example for 
> compiler renesas (R8C) I wrote as follows in the file:
> c:\Programmi\eclipse\plugins\si.isystem.regExErrorParser_1.0.8.i9_9_72_20090403_134038\plugin.xml
> 
> <extension
>          id="mitsubishi.id.for.err.parser"
>          name="MITSUBISHI Error Parser"
>          point="org.eclipse.cdt.core.ErrorParser">
> 
> <errorparser class="si.isystem.regexerrparser.RegExErrorParser"
>                      config="regex/MITSUBISHIExpresions.properties"/>
> </extension>
> 
> then in the file 
> c:\Programmi\eclipse\plugins\si.isystem.regExErrorParser_1.0.8.i9_9_72_20090403_134038\regex\MITSUBISHIExpresions.properties 
> I wrote (for errors):
> 
> error =  1, 2, 3:Error[a-z0-9\.\(\)]*:(.+), *line ([0-9]+)\](.*)
> 
> Regards
> Paolo
> 
> Il 11/11/2009 10.43, Eclipse_Keil ha scritto:
>> Hi Paolo,
>>
>> how did you get RegexErrorParser from isystem to work?
>>
>> Thanks
>> Mike
>>
>>
>> Paolo Nenna wrote:
>>    
>>> Hi, I have found regex error parser for CDT 6 at this address and it
>>> seems to work well:
>>>
>>> http://www.isystem.com/content/0/288/
>>>
>>> I had some difficult to write the correct regex expression. I don't work
>>> with keil, but I have worked with codewright in the past, so I know very
>>> well your problem, then I have changed because I want to work with an
>>> open source editor and Eclipse is a great open source editor.
>>>
>>> Best Regards
>>> Paolo
>>>
>>> Eclipse_Keil ha scritto:
>>>      
>>>> 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.
>>>>
>>>>        
>>> _______________________________________________
>>> 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--tp26215807p26315078.html
Sent from the Eclipse CDT - Development mailing list archive at Nabble.com.



Back to the top