[news.eclipse.tools.cdt] Re: OK, I give - how do I make indexing work?

[Doug Schaefer <dschaefer@xxxxxxx>]

Keath Milligan wrote:
> Using Eclipse 3.1 + CDT 3.0 on Windows (I get the same behavior under 
> Linux as well).
>
> I have a large, pre-existing project (thousands of files) that I am 
> trying to incorporate Eclipse into. So far, I've managed to get basic 
> development and source-level debugging working, but I can't get any of 
> the following search-related features to work:
>
> Open Definition
> Open Declaration
> All Declarations
> All References
>
> All References will only find references within the file I am currently 
> editing, but no where else. All of the other functions return nothing.
>
> All of the involved source files and headers are within the project. 
> I've tried explicitly setting include paths, source paths and binary 
> paths all to no effect. I've tried automatic discovery of paths and 
> symbols and CTags vs Full Indexing. I've tried recreating the project in 
> a variety of different ways - all to no avail.
>
> At this point, I'm looking at the CDT source code trying to figure out 
> how the indexer works, but it sure would be nice if someone in the know 
> could write a document on getting this to work with REAL WORLD projects 
> beyond the simplistic Hello, World examples in the current docs.

Yes, a document is desperately needed. Dealing with large legacy 
projects is definitely a challenge that we have. I have been able to get 
things to work with the Mozilla source code using the scanner discovery. 
It has around 16000 files.

It sounds like you are doing the right things with telling the CDT about 
the paths. Did you try per file scanner discovery. I seem to have better 
results with that. Also, the scanner discovery works by parsing the 
build output. If your makefile hides the commands (such as the Linux 
kernel 2.6 does) it won't work.

Hope this helps,
Doug