Wasn’t mentioning
this: I refresh and index the whole workspace. Then the search is working
fine. I close eclipse, and restart it again. There is no error in the error
log. Granting the CDT all the time to initialize, and then doing the search is
what is having the problem. The search seems to improve with the number of
“projects I visit by working on” (not changing or rebuilding the index
whatsoever).
Jens.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Schorn, Markus
Sent: Donnerstag, 22. Oktober 2009
17:03
To: CDT General
developers list.
Subject: RE:
[cdt-dev] Large Workspace and C/C++ Search
Try refreshing your
workspace! The indexer does not look at your file-system it takes
whatever is reported by the
resources
plugin.
Markus.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Elmenthaler, Jens
Sent: Thursday, October 22, 2009 4:00
PM
To: CDT General
developers list.
Subject:
[cdt-dev] Large Workspace and C/C++ Search
Importance:
Low
Hi
all,
I have a large C/C++ workspace
with about a 100 projects and a couple of million lines of
code.
After starting my eclipse the
C/C++ search actually responds immediately and does not find anything. This
is true for quite some element names, but not all. After going into the
project explorer and expanding projects, the C/C++ search yields many more
hits for elements names of those projects.
Is there any deferred
initialization that gets triggered by expanding a project? Is my workspace
too large exceeding some limits? What should I look
for?
Regards,
Jens.