|
|
|
|
|
Re: Indexer's extern "C" confusion [message #1782759 is a reply to message #1782754] |
Thu, 01 March 2018 06:14 |
David Vavra Messages: 1426 Registered: October 2012 |
Senior Member |
|
|
The index is merely a database. It's up to the discovery providers and scanner to fill it.
The built-ins provider is the one to fill in predefined macros.
Since you don't have one, you need to do it manually.
What you might want to consider is a file that contains the definitions and add it as a user entry in
Project --> Properties --> C/C++ General --> Preprocessor Include Paths, Macros etc.
You might want to file an enhancement request in Bugzilla to have built-in defaults for standard macros.
[Updated on: Thu, 01 March 2018 06:52] Report message to a moderator
|
|
|
Re: Indexer's extern "C" confusion [message #1782773 is a reply to message #1782759] |
Thu, 01 March 2018 09:17 |
Tauno Voipio Messages: 742 Registered: August 2014 |
Senior Member |
|
|
I had an analogous problem with cross-compilation to a Cortex-M4 ARM. There are actually hundreds of predefined constants in the compiler (351 for Cortex-M4) in addition to the __cplusplus.
I pushed the GCC to create a header file of the includes:
arm-none-eabi-gcc -mthumb -mcpu=cortex-m4 -E -dM >cortexm4-predef.h
and added it to the indexer includes.
Many of the standard library headers depend on the constants in the predefinition file, and this keeps the indexer happy with them.
--
Tauno Voipio
|
|
|
Powered by
FUDForum. Page generated in 0.04494 seconds