Eclipse Community Forums: C / C++ IDE (CDT)

Home » Language IDEs » C / C++ IDE (CDT) » Indexer activation

Mon, 02 August 2004 15:50

Eclipse User

Is there a way to explicitly (re-)activate the Indexer on a managed project.

Adding a path to the project directories does not trigger an update, so it
seems to be necessary to close and re-open the project.

Is there a way to (re-)activate the indexer just on selected files (while
diagnosing problems and so avoiding indexing of another 1000)?

The user manual refers to an Indexer bar. Is this obsolete, since under
Eclipse 3.0 there is only a transient progress contribution?

Regards

Ed Willink

Re: Indexer activation [message #114240 is a reply to message #113460]

Thu, 05 August 2004 13:28

Eclipse User

Hi Ed -

Due to some changes to the event model, Managed build path updates do not
currently trigger reindexes. This is a defect - please raise a bug in
bugzilla for this.

There are a number of workarounds available:

- You can use the problem markers (right click on Project->Properties->C/C++
Indexer->enable preprocessor problems at the
very least, all 3 types if you wish). This will show you where the problems
are in the files. Correcting them (adding your include paths) and
resaving the file will force a re-index.

- When you first create the project you can choose to turn indexing off.
This is useful if you have an existing codebase that you wish to import. You
can then setup the necessary include paths and turn on indexing which will
force a re-index.

- You can use a Standard Make project. Standard Make projects allow you to
designate
source folders (which are indexed). In this way you can index only a subset
of a large project.
Standard make also reacts to path changes, re-triggering the indexer on
updates.

"Ed Willink" <ed@willink.me.uk> wrote in message
news:cem5qb$n8e$1@eclipse.org...
> Is there a way to explicitly (re-)activate the Indexer on a managed
project.
>
> Adding a path to the project directories does not trigger an update, so it
> seems to be necessary to close and re-open the project.
>
> Is there a way to (re-)activate the indexer just on selected files (while
> diagnosing problems and so avoiding indexing of another 1000)?
>
> The user manual refers to an Indexer bar. Is this obsolete, since under
> Eclipse 3.0 there is only a transient progress contribution?
>
> Regards
>
> Ed Willink

Previous Topic:	C++ indexer warning messages won't go away
Next Topic:	C/C++ Indexer very slow

Goto Forum:

-=] Back to Top [=-

Current Time: Wed May 07 21:48:09 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter