|
|
|
|
|
Re: Excluded files from build still included in codan [message #1756345 is a reply to message #1756338] |
Wed, 15 March 2017 11:57  |
Eclipse User |
|
|
|
You have a missing definition: CONFIG1 is undefined.
Actually, its definition status will likely be hit or miss.
I have a C file where the definition comes and goes.
The Indexer doesn't handle defines very well
Because of caching, a dependent preprocessor definition might be wrong.
If the Indexer thinks the CONFIG1 is undefined then so will CODAN.
To make this always work with CODAN, you could try
#if defined(CONFIG1) || defined(__CDT_PARSER__)
typedef unsigned long ulong;
#endif
This will force the code block to be included when the CODAN reads the file.
This could be a real nuisance if you have a lot of them.
The key though is to make the file stand alone without errors when CODAN looks at it.
|
|
|
Powered by
FUDForum. Page generated in 0.04961 seconds