AW: [cdt-dev] "Open Declaration" (hardly ever) works for large standard

["Ploett, Norbert" <norbert.ploett@xxxxxxxxxxx>]

Hello Doug,

> The standard first question I ask when someone reports things like this is:

Yeah well, (blush) actually there are only the auto-discovered paths set. Also I have not defined any source folders (so that the project directory is the default source folder) 
Auto-discovered paths are some  /usr/... and the ecos kernel's header files. That's pretty good.

And also ...

The path structure for my example is as follows:

<project dir>
 +- sock
	+- cfg
	|	+- sock_inc.h
	+- src
		+- sock_usr.h
		+- sock_u.c

sock_u.c locally includes sock_inc.h:
#include "../cfg/sock_inc.h"


sock_inc.h locally includes sock_usr.h:
#include "../src/sock_usr.h"

So this is actually included around two corners, but does not require any include path settings for the compiler.
Also during my debugging sessions I have seen that the file is found and parsed. The problem seems to be in resolving the binding correctly later when the IASTName is searched for. Can this also happen due to missing path settings?

Anything more I can do for you?
Is there any documentation about the working of the the AST / DOM / parsing and binding framework?

Greets


Norbert Ploett


-----Ursprüngliche Nachricht-----
Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Doug Schaefer
Gesendet: Mittwoch, 14. September 2005 17:53
An: CDT General developers list.
Betreff: RE: [cdt-dev] "Open Declaration" (hardly ever) works for large standard make project

The standard first question I ask when someone reports things like this is:
Are your paths set properly in the project properties. Without knowing where
to find include files, parsing is tremendously difficult.

There are some architecturally things I'm looking at that should hopefully
make us more robust and faster. But at the end of the day, we will still
need to know where to find the external header files (or be able to import a
prebuilt PDOM database, but more on that later...).

Doug Schaefer
Senior Software Developer
QNX Software Systems

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Ploett, Norbert
> Sent: Wednesday, September 14, 2005 10:58 AM
> To: CDT General developers list.
> Subject: [cdt-dev] "Open Declaration" (hardly ever) works for large
> standard make project
> 
> Hello folks,
> 
> in a project I am working on code navigation is very unreliable. I have
> drilled
> into the behavior of "Open Declaration", which functions only for rare,
> non
> reproducable examples. Here are some more details of my setup:
> 
> Host OS: Linux
> CDT Version: 3.0 Release
> Project Type: Standard Make C++
> The project contains some 4.500 files - the eCos OS plus an application.
> The eCos sources are linked into the project with a linked folder.
> 
> More details are in https://bugs.eclipse.org/bugs/show_bug.cgi?id=109506
> 
> Now I only (at most) half understand what is going on. I do not think it
> will be practical to supply the big project due to it's sheer size. I am
> very willing to supply more details and help further if someone who
> understands the workings of the AST framework will comment on this.
> 
> Is there any design documentation for the DOM/AST framework?
> 
> Regards,
> 
> 
> Norbert Ploett
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev