|
|
Re: Hyperlinkig problem [message #151245 is a reply to message #151236] |
Tue, 16 August 2005 15:03 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: ddaoust.ca.ibm.com
Problems like this are almost always include path or symbol problems.
You can either allow CDT to discover your paths and symbols (based on a
build), or you can manually enter them.
I would suggest that you try a simple example and see if you can make it
work -- sometimes when you use an existing code base, you will run into
unreported defects with the CDT, and this may confuse the issue.
Note that I have no problems with *Internal* or *External* paths -- both
work fine for me. If someone has problems with them, it would be nice to
see a defect number. (and, of course, a reproduceable problem description)
-Dave
"Patrick Turley" <pturley@pturley.com> wrote in message
news:ddsto8$f8o$1@news.eclipse.org...
> Kunwardeep wrote:
> > Hi
> > I am using CDT 3.0 with Eclipse 3.1 on a windows platform.I belive in
> > the new CDT we can use ctrl+F3 to navigate to the function "definition".
> >
> > http://dev.eclipse.org/newslists/news.eclipse.tools.cdt/msg0 8057.html
> >
> > But i somehow cant get it to work.Any suggestions?
> >
>
> In my experience, the real problem is that the indexer doesn't have a
> full understanding of your code yet. Also in my experience, this is
> usually because you are using *Internal* rather than *External* include
> paths.
>
> Open your project properties. Look for C/C++ Include Paths & Symbols.
> Any of the elements on the include path shown here that are *Internal*
> entries are unusable. Instead, make them *External*, even if they appear
> within your project. For some reason, the internal ones are bugged.
|
|
|
Powered by
FUDForum. Page generated in 0.03670 seconds