I\'ve just started using Eclipse Indigo (coming from Galileo) and I\'m getting little red bugs in the gutter for every use of size_t.
If your toolchain can compile the code with only its default include paths and symbols, just setting Eclipse to use them should be enough. Go to C/C++ Build -> Discovery Options
in the project properties, and for each language, change the Compiler invocation command
from the native compiler (e.g. g++
) to your cross compiler (e.g. C:\nburn\gcc-m68k\bin\g++
perhaps?). Then on the next build, the auto-discovery will run and update the so-called "built-in" paths and symbols that show up in the project's C/C++ General -> Paths and Symbols
to whatever your compiler reported, and you can re-index again to make sure any warnings for the old "built-ins" are gone.