Eclipse 3.7 cannot resolve Types in C++ Editor
c++, eclipse, ide, indexer
Solution
The red underlines for common types are usually caused by not having your standard library in your include path. Look at your includes for your project... they are in the project properties. Ensure that your C++ includes have an entry that matches the C++ standard libs folders for the compiler you are using.
Problem
I recently changed from Eclipse 3.6 to Eclipse 3.7 , which I am using for C++ development in Ubuntu 11.04 . With Version 3.6 I had no big troubles, except that I always had some issues with the indexer. Now with Version 3.7 it begins marking unresolved Types as Errors. Since the indexer seems to dislike me even more, my Eclipse apparently doesn't know types like `uint16_t` or `size_t`. In contrary to the displayed errors in the code editor, my compiler has no problems with compiling the code and resolving all symbols and types, so this seems to be a problem of the IDE itself. Are there any ways to avoid this behavior, because all the red underlines make my code more and more unreadable...? Update: Okay with some research and the answer from Dennis I found out that I need to add some paths to `Project Properties/ C/C++ General/ Paths and Symbols` Since I am building for a PowerPC instead of a I32 target, I can not just add `/usr/include` . Instead I needed to add `/usr/powerpc-linux-gnu/libc/usr/include` for all the standard headers (like `stdint.h`). Also I needed: `/usr/lib/gcc/powerpc-linux-gnu/4.5.1/include` for the `stdarg.h`. Now almost all the errors are gone. The only function which still troubles me is `printf` from the header `stdio.h`. I looked it up and the header file itself lies within the included paths. Still I get an Error which says `Function printf could not be resolved`. I want to note again, that these are just errors displayed by Eclipse - The compiling itself works fine. So this actually throws up 3 questions: In the project properties the `Paths and Symbols` section coheres with the include Paths out of the `C++ Build/Settings/C++ Includes` section. This means adding/deleting a path in one of those sections directly affects the entry of the others. Since the `C++ Includes` directly coheres with the Compiler I wonder why the compiler can compile correcty ( and finds the headers ) even if they arent passed to him as a path? Is there some kind of standard path GCC uses, which I don't know about? Why doesn't he find `printf` in eclipse? The headerfile `stdio.h` is included and it also contains the declaration of `printf` - so why does the Eclipse Code Editor tell me that it can't resolve it? Why are the header files divided so much? I am aware that I need other header files if I am building for another traget (e.g. PowerPC) - But why does the GNU GCC separate those headers in different dirs?