Include question

Ian Roxborough
Fri Jan 25 19:12:00 GMT 2002


Source-Navigator should resolved the header file dependancies
automatically.  Can you see "port.h" in the symbol browser?

It might have a problem finding port.h if you can't see it
in the file/symbol browser.

There is a bug where if port.h is included in a2d.h and not
a .c file SN will have a problem finding port.h.

If you go to the includes section of compiler settings in 
the target editor then you can manually enter paths to be
search for includes.


On Thu, 24 Jan 2002 13:14:40 -0500 (EST) speedy2 <> wrote:
> Hello all.
> For a project I am working on,("testproj") I have split my code into
> blocks(like "a2d" and "port") and put them in a directory structure like:
> \testproj\port\port.c
> \testproj\port\port.h
> \testproj\a2d\a2d.c
> \testproj\a2d\a2d.h
> Files like a2d.c end up including port.h with a simple #include port.h
> Of course gcc does not compile because port.h is not in the path and the
> only fix is to hardcode the include or do it relatively like
> "../port/port.h"
> Is it possible when setting up Source Navigator to build, to get it to
> find dependant files and automatically invoke gcc with the right options?
> That way in my a2d.c file I can leave the include as:
> #include "port.h"
> and allow SNAV to figure it out?
> Thanks,
> Speedy2.

More information about the Sourcenav mailing list