Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Macros defined in Language are not taken into account by the parser

Hello Andew,

I guess I don't have it ... I have the following providers only:
- CDT User Settings Entries
- CDT Managed Build Setting Entries
- a specific provider for the compiler, used only to add an compiler internal symbol

How can I add the Language Settings Provider?
"Previous functionality" in your mail sounds like that this is no more the recommended way to implement this!? Is there a new way to configure the scanner, replacing ScannerExtensionConfiguration?


Date: Fri, 5 Jul 2013 12:30:25 -0400
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Macros defined in Language are not taken into account by the parser

Hi Sebastian,
Do you have MBS Language Settings Provider defined in your toolchain? All previous functionality related to supplying macros should be preserved when using this provider.


On Fri, Jul 5, 2013 at 11:34 AM, Sebastian Wagner <se.wagner@xxxxxx> wrote:

I moved my toolchain plugin from Eclipse 3.7 to 4.3. Sources are identical, except that in 4.3 I used the LanguageSettingsProvider extension point.
In my plugin I defined a new language based on GCC and added some keywords and macros using addKeyword() and addMacro(). This worked fine with the old version, but in the new one the macros are no longer recognized. They appear correctly, means they are highlighted in the source as a keyword. Nevertheless, they are not resolved since the macros are not taken into account.
I checked the parser log and the macros are missing there, but appeared in 3.7. I set some breakpoints to see if the instance of IARCScannerExtensionConfiguration is retrieved correctly and if it contains all data. I followed some steps and checked the variables - it seems that the macros are included.

Can someone give me a hint where to look at? It seems that my language is taken into account, the language name also appears correctly in the parser log. But the macros are not considered.

best regards


cdt-dev mailing list

_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx

Back to the top