Re: [cdt-ui-dev] Problem with Make Targets entries

["Fedja Jeleskovic" <mrawd2@xxxxxxxxx>]

One more question regarding the same subject. Most of our files are included as following:
#include <my_include_files/MyClass.h>

And directory structure is:
project/include/my_include_files
project/source

All of the include files are in the my_include_files folder, while the source files are in the source folder.

In my project paths, I have added extra include path from the workspace like:
MY_PRJ/project/include

The question here is whether having a long path for the include directive have something to do with this?

Thanks


Fedja

On 3/12/07, Leherbauer, Anton <Anton.Leherbauer@xxxxxxxxxxxxx> wrote:

Yes, that's possible. The open include action searches the whole project as a fallback if it cannot find the file on the include search path.

 

Toni

---

From: Fedja Jeleskovic [mailto:mrawd2@xxxxxxxxx]
Sent: Monday, March 12, 2007 3:31 PM
To: Leherbauer, Anton
Cc: cdt-ui-dev@xxxxxxxxxxx
Subject: Re: [cdt-ui-dev] Problem with Make Targets entries

So, even though, when I double click on the include file with the yellow triangle and it opens up correctly, some other paths might be wrong. Right?


Fedja

On 3/12/07, Leherbauer, Anton <Anton.Leherbauer@xxxxxxxxxxxxx> wrote:

> Another issue that I would see with newer versions of the CDT
> is addition of the little yellow triangle on all of  (actually
> like a subscript before the file name) include files from the
> Outline window. Is there any explanation for this?

This is a new feature which indicates unresolved includes reported
by the parser.
While you may be able to successfully build your project, the
parser/indexer does not get the correct include paths.
Depending on your project type you may have to edit the include
paths by hand. If you haven't had issues with unresolved includes
before, this might also be a side-effect of the conversion
to the new build system.

HTH,
Toni
--
Anton Leherbauer
Wind River CDT Team, Austria