| Open definition not working. Bug or stupidity ? [message #184827] |
Thu, 15 February 2007 16:41 |
Eclipse User |
|
|
|
Originally posted by: leonardopsantos.gmail.com
Hi Everybody! I'm having a curious issue with Eclipse+CDT and as I can't
find a solution googling around, I decided to post here.
I'm a C developer working with uClinux in a microblaze processor in a
Linux workstation. I've been using Eclipse 3.1.2+CDT 3.0.2 for some time
now and they work fine. I'm able to add my projects and use the "Go to
definition" very well. But now I'm trying to use Eclipse 3.2.1+CDT 3.1.1
and the "Go to definition" feature just won't work.
All my projects are "Standard make" projects and adding the mb-gcc
compiler to the PATH ( Project->Properties>C/C++ Make Project->Environment
) makes everything compile correctly. I get no indexing problems.
I have a library and some applications. The library's .h files are include
with an absolute path ( #include "../mycustomlib/some_file.h" ), e.g., I
don't pass the -I flag to GCC.
When I create the apps project's, I always check the box for the library's
project at the Project References window. When I'm working on the library,
the "Go to definition" feature works fine. If I hit crtl+g ( search for
declarations ) inside the library, I get two results, one for a .h file -
where it's declared - and one for a .c file - where it's implemented. But
if I do the same thing for the same library function but inside an
application it only finds the .h declaration - F3 works but ctrl+F3
doesn't! Doing the same search in the lib funcion from the app project -
but using the Eclipse and CDT older versions - works, I get one result for
the .c and another to the .h file.
I'm not sure what I'm doing wrong:
1) uClinux uses a FLAT binary format, not ELF. Do I have to setup-up
something else ? From what I read, there were optimizations to the parser
between versions. That means that the new parser might be sensible to some
configuration/variable/whatever and that the older wasn't ?
2) The fact that I get two declarations while searching inside the library
and that "Go to definition" works indicate that the parser is working
correctly ?
3) If I find the function declaration in the .h file from the app project
means that the include path discovery is working correctly ?
4) As I think (2) and (3) are true, why "Go to definition" is not working
? That seems sufficient to the older versions.
I tried to run Eclipse with Sun's Java 1.4.2.12 and 1.5.0.5 with the same
results. I had no luck looking the log file either, nor running Eclipse
with -consolelog -debug.
Any help is greatly appreciated. Thank you!
|
|
|
Powered by
FUDForum. Page generated in 0.04234 seconds
Home