| Indexer doesn't recognize #ifdef after compilation [message #1065320] |
Tue, 25 June 2013 06:16  |
Eclipse User |
|
|
|
Hello,
I am compiling a project in Juno 4.2.2 where i have some #ifdefs defined at compile time.
The project compiles and runs successfully, but the activated #ifdefs remain greyed out in the code editor and i get unresolved conflicts because the functions inside the #ifdef are not accessed by the indexer.
If i add the #ifdef symbol to the indexer, the problem is solved, but in previous versions of eclipse these symbols were added after compiling...
Was there any change? Or something else i can do to have that behaviour again?
|
|
|
|
|
|
|
| Re: Indexer doesn't recognize #ifdef after compilation [message #1124586 is a reply to message #1066134] |
Thu, 03 October 2013 13:44  |
| Eclipse User |
|
|
|
Sorry for ressurecting this thread, but I have the same problem with the same project now that I have updated to kepler. I had included the most important symbols previously, hence i didn't followup the thread, but my mind does not rest while this problem still exists.
To answer your question: Yes, both folders are from the same project.
Furthermore, on a same folder, some files have the gcc build output parser work and give them the symbols, while others don't. I can notice that most of the files that have the symbols are .cc ones, while no .h being compiled has symbols added by BOP.
|
|
|
Powered by
FUDForum. Page generated in 0.04594 seconds
Home