IDE would see files only if they are in one of the IDE's projects. Putting them in workspace is not enough.
If you want to have headers separately just create a project and specify as location of your project where the headers 
are. You can create it as "makefile" project with dummy make.
You can refer to them using project variables instead of absolute path in this case.

On 24/11/10 09:56 AM, Robert Murrell wrote:
> Can someone confirm if the following are known bugs in the IDE?
> 
>  I have include files that are stored in subdirectories under the workspace directory but not in a project.  The path 
to them is absolute.  The compiler finds the files when building.
> 
> The editor can't find include files in the "extra include paths".
> 
> When I edit one of these files and then build the project, the file is automatically saved but make does not detect 
the change.  I have to force a rebuild of the whole project to incorporate the changes.
> 
> I have all these external source and include files in one directory and have to add both an extra include and extra 
source path to the project to get the editor and compiler to recognize them.  This causes double references in the 
project for each file and confusion as to which one should be opened for editing.  I would like to be able to separate 
the source and include files into separate directories.  And since they are stored under the workspace, I would like to 
be able to reference them relative to the workspace instead of using absolute paths.
> 
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post75788
> 

Hi, Robert,

See some replies ([cwd]) in-line, below.

HTH,

Christian


On 10-11-24 9:56 AM, "Robert Murrell" <community-noreply@qnx.com> wrote:

> Can someone confirm if the following are known bugs in the IDE?
> 
>  I have include files that are stored in subdirectories under the workspace
> directory but not in a project.  The path to them is absolute.  The compiler
> finds the files when building.
> 
> The editor can't find include files in the "extra include paths".
> 
> [cwd] Is this a "QNX C Project"?  If so, then the C/C++ index should have
> these include paths injected into it.  If not, it may be a bug.  If your
> project is a regular makefile project, then you will have to tell the indexer
> about the include paths yourself, in the "C/C++ General -> Paths and Symbols"
> page in the project settings.
> 
> 
> When I edit one of these files and then build the project, the file is
> automatically saved but make does not detect the change.  I have to force a
> rebuild of the whole project to incorporate the changes.
> 
> [cwd] This is normal when not using gcc's dependency-checking features.  Try
> enabling the "User Headers" option in the "Dependency Checking" sub-menu of
> the context menu on your project.
> 
> 
> I have all these external source and include files in one directory and have
> to add both an extra include and extra source path to the project to get the
> editor and compiler to recognize them.  This causes double references in the
> project for each file and confusion as to which one should be opened for
> editing.  I would like to be able to separate the source and include files
> into separate directories.  And since they are stored under the workspace, I
> would like to be able to reference them relative to the workspace instead of
> using absolute paths.
> 
> [cwd] Does referencing them relative to $(WORKSPACE_ROOT) in your makefile not
> work (if QNX C Project).  Otherwise, relative paths should work, too.  You
> should be able to separate the headers from the source files.  Is there a
> reason why you don't?
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post75788
> 
> 

OK IDE people, attached is a zip of a simplified workspace of my environment.  The goal is to build project_a and 
project_b so that each displays its unique banner message.  My environment is QNX 6.5.0 and Momentics 4.7.0.  Here are 
the requirements:

1. No absolute paths.

2. The editor can find all symbols and files without any red or yellow squiggly lines.

3. If ANY file, local or external, source or include, in a project is edited, when the project is built, the editor 
saves the changed file, make detects the change, and the compiler builds the project.

If you can do this, please let me know how to do it.