| Need help with indexer errors [message #108497] |
Thu, 01 July 2004 13:55  |
Eclipse User |
|
|
|
Features like open declaration, content assist, and search are not working
for me most of the time so I'm trying to eliminate all the C/C++ Indexer
problems
in the hopes that that might fix it. I think I have all the header files
being read now and am down to 40 or so errors of one of following two forms:
Severity Description
1 C/C++ Indexer Problem: Syntax error encountered in file: sem.c on line:
412.
1 C/C++ Indexer Problem: Macro usage error for macro : MB in file: aggrsp.c
on line: 404.
All the source builds fine with our C compiler of course, so either the
indexer
has bugs handling our syntax or I have not correctly set up the 48 defines
and 20
include paths needed to correctly resolve all the types and macros.
Unfortunately with these brief error messages I haven't got a clue which it
is.
Is there some debug trace option or something I could turn on to try to
figure out
what the Indexer is thinking when it produces these errors? For example,
what is the
current definition of the MB macro? Is it bad because it's not defined or
has too
many or too few arguments or something else? What tokens was it expecting in
sem.c?
What does the macro expanded version of the line look like?
Also, is there a way to make the indexer run only on a single source file?
It can take
up to an hour to run over all 170 files in the project plus headers on the
network
which really makes trial-and-error kind of painful.
Thanks,
--Ed
|
|
|
|
|
| Re: Need help with indexer errors [message #109730 is a reply to message #109522] |
Wed, 07 July 2004 10:09  |
| Eclipse User |
|
|
|
You do not necessarily have to use the CDT to build your project as much
that you need to make sure that you have a means of letting CDT discover
build-information.
That being said, you raise a good point about allowing external
contributions to the index, I would suggest you raise a feature request for
it.
Thanks
JohnC
"Ed Burnette" <ed.burnette@sas.com> wrote in message
news:ccfgu6$304$1@eclipse.org...
> No, we have our own build program which is vaguely like a distributed
make.
> Haven't gotten to the build integration part yet. For now I'm using a
custom
> plug-in but I had hoped to eventually hook into the CDT building and error
> parsing mechanism.
>
> Looks like the indexer is not going to be usable for us in this release.
If
> you had a way to support external indexes, we already run a ctags-like
> utility over all the source and have a symbol server set up that could be
> tied into.
>
> --
> Ed
>
> "johnc" <jcamelon@ca.ibm.com> wrote in message
> news:ccbfkr$gaq$1@eclipse.org...
> > Hi Ed,
> >
> > Thanks for your involvement w/CDT over the past week, you've raise a lot
> of
> > good bugs!
> >
> > How are you building your project? Standard Make w/the discovery
feature?
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.07626 seconds
Home