Eclipse Community Forums: DSDP - Target Management » Invalid project path: Include path not found

Help

Home

Home » Eclipse Projects » DSDP - Target Management » Invalid project path: Include path not found

Show: Today's Messages :: Show Polls :: Message Navigator

Invalid project path: Include path not found [message #33476]

Fri, 20 March 2009 12:12

ilya

Messages: 14
Registered: July 2009

Junior Member

I have latest Eclipse 3.4.2 with CDT 5.0.2 and RDT 1.0
I successfully created remote project but when I enter remote include
directory - either /usr/include or workspace's /include, then I get the
warning e.g.:
Invalid project path: Include path not found (\usr\include)

Also I get warning
Error launching external scanner info generator (gcc .....)

due to this I cannot build class trees and resolve symbols in my project.
I tried to google the problem and found many similar descriptions but no
solutions neither workarounds

Report message to a moderator

Re: Invalid project path: Include path not found [message #33577 is a reply to message #33476]

Mon, 23 March 2009 10:54

ilya

Messages: 14
Registered: July 2009

Junior Member

Some updates.
It looks like indexing works on UNIX side despite on the warning message.
But anywat there are problems with it. It indexes direct headers contained
in cpp files. Here is a scenario:

symbol LOG_IT is defined in a.h but a.h is not included in main.cpp.
Instead b.h is included while a.h is included in b.h. In this case LOG_IT
cannot be resolved

Report message to a moderator

Re: Invalid project path: Include path not found [message #33846 is a reply to message #33577]

Thu, 26 March 2009 00:27

Martin Oberhuber

Messages: 1007
Registered: July 2009

Senior Member

Hi Ilya,

this is the wrong newsgroup. The RDT folks hang out on
eclipse.tools.cdt or
eclipse.tools.ptp
I'm not sure which.

Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm

ilya wrote:
> Some updates. It looks like indexing works on UNIX side despite on the
> warning message. But anywat there are problems with it. It indexes
> direct headers contained in cpp files. Here is a scenario:
>
> symbol LOG_IT is defined in a.h but a.h is not included in main.cpp.
> Instead b.h is included while a.h is included in b.h. In this case
> LOG_IT cannot be resolved
>
>
>

Report message to a moderator