| How to have the indexer run without a build [message #145043] |
Wed, 11 May 2005 08:46  |
Eclipse User |
|
|
|
Originally posted by: johnny.wezel.ubs.com
I have a project (standard make directly on a source tree) which has
probably no chance to be built under Eclipse because the make is depending
on many environment variables (or is there a way to set env vars for
builds?).
Anyway, I want to use Eclipse for browsing and editing sources and I'll be
happy to run make in some shell.
But the indexer won't run without a build. How can I force the indexer to
run without the build?
Cheers,
Johnny Wezel
|
|
|
| Re: How to have the indexer run without a build [message #145384 is a reply to message #145043] |
Fri, 13 May 2005 08:58  |
| Eclipse User |
|
|
|
Johnny -
The indexer is not tied to the build in any way. In fact, closing and
reopening a project will
trigger a reindex.
If you're using CDT 3.0 M6 or the latest from head, you can use either the
Original Source Indexer, DOM Indexer
or CTags Indexer. If you don't care about cross reference info (which is
used for search for
references) your best bet is to use the CTags indexer which is by far the
fastest of the indexers.
More info (from a previous posting):
> * Original Indexer - this is the indexer that has been released with
> previous version of the CDT based on the initial version of the CDT
parser.
>
> Advantages - Full information parse information (references,
declarations,
> definitions), stable
>
> Disadvantages - Slow (which is especially problematic if you're trying
to
> import a large existing code base into the CDT; if you're starting from
> scratch on a new project, it's reasonable)
>
> * DOM Indexer - this is an indexer based on the new CDT parser
>
> Advantages - Full parse info (references, declarations, definitions);
> Correctness of parse info is improved over the original indexer
>
> Disadvantages - Slower than the original in M6 but that's slated for a
tune
> up come M7
>
> * CTags Indexer - Makes use of Exuberant CTags (5.5.4 recommended)
>
> Advantages - Really Fast
>
> Disadvantages - No cross reference information (can't perform search for
> references)
>
|
|
|
| Re: How to have the indexer run without a build [message #145401 is a reply to message #145384] |
Fri, 13 May 2005 11:19 |
| Eclipse User |
|
|
|
Of course without a build there will have been no chance for the CDT to
automatically discover the paths/symbols that would be necessary to
correctly parse your source, so the results of the index may not be
complete/correct.
You could either
1) manually input the appropriate paths/symbols in the project properties.
2) fake a build by recording the output of a real build and then having the
making called by the cdt build just cat those results to the stdout.
-Andrew
So you would either need to "Bogdan Gheorghe" <gheorghe@ca.ibm.com> wrote in
message news:d628qf$vnt$1@news.eclipse.org...
> Johnny -
>
> The indexer is not tied to the build in any way. In fact, closing and
> reopening a project will
> trigger a reindex.
>
> If you're using CDT 3.0 M6 or the latest from head, you can use either the
> Original Source Indexer, DOM Indexer
> or CTags Indexer. If you don't care about cross reference info (which is
> used for search for
> references) your best bet is to use the CTags indexer which is by far the
> fastest of the indexers.
> More info (from a previous posting):
>
>
> > * Original Indexer - this is the indexer that has been released with
>
> > previous version of the CDT based on the initial version of the CDT
>
> parser.
>
> >
>
> > Advantages - Full information parse information (references,
>
> declarations,
>
> > definitions), stable
>
> >
>
> > Disadvantages - Slow (which is especially problematic if you're trying
>
> to
>
> > import a large existing code base into the CDT; if you're starting from
>
> > scratch on a new project, it's reasonable)
>
> >
>
> > * DOM Indexer - this is an indexer based on the new CDT parser
>
> >
>
> > Advantages - Full parse info (references, declarations, definitions);
>
> > Correctness of parse info is improved over the original indexer
>
> >
>
> > Disadvantages - Slower than the original in M6 but that's slated for a
>
> tune
>
> > up come M7
>
> >
>
> > * CTags Indexer - Makes use of Exuberant CTags (5.5.4 recommended)
>
> >
>
> > Advantages - Really Fast
>
> >
>
> > Disadvantages - No cross reference information (can't perform search for
>
> > references)
>
> >
>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03126 seconds
Home