Hello,
robmilne wrote:I did spend time trying to add include paths to properties->C/C++ General->Code Ananlysis->Paths and Symbols but wasn't successful in removing the eclipse errors. I'm using windows so the forward-reverse slash is also a source of confusion. I will give it another try.
Do you mean
Project properties->C/C++ General->Paths and Symbols (i.e. without
Code Ananlysis) as attached?
It should be the right place to add references to external .h files. Note that there is a set of "include directories" for each language and (at least in my case) the default one is
Assembly, than if you have to select
GNU C before add the reference (or add it to all languages).
Complex projects have also mode than one
Configuration, than you have to be sure to add the reference to all configuration that need it.
As last point (probably a stupid point), the path of
include directory and the path/name in the
#include <..> directive should work together, i.e. the concatenation of both is the path in the filesystem of the required file.
After everything work, you can add more flexibility to your project using variables, as shown in the attached image. In this way you can move the project on distinct computers without change it (just adjust the environment/eclipse variable value).
A complete different approach is to "link" the include file/directory to your project. The easiest way to do it it to drag the file/directory from the filesystem browser (like explorer) and drop it inside the eclipse "project explorer" view in the eclipse gui (or similar views, like "project navigation" view); doing that, eclipse ask if link or copy the file/directory. Also in this case, be sure that the path relative to the project root is compatible with the content of the
#include <..> directive.
Even if is a little more complex, also links can be done through variables.
The main difference between two approaches is that the first one searches only .h files and consider them read-only files, while the second one shows all files and considered them as project files (you can modify them as you want, and there are more eclipse functionalities that can be apply on them).
Regarding the list of eeopts, as told by Paolo, there is not a complete list of all valid options. First places where search are the wiki and the
Active OIL Implementation view. Note that RT-Druid 2.0 contains a new editor with content assist, providing the list of valid options in a specific point of the oil file (the default shortcut is
crtl-space)
Regards,
Nicola