Home » Language IDEs » C / C++ IDE (CDT) » Hyperlinking (open declaration/definition) problems
| Hyperlinking (open declaration/definition) problems [message #149714] |
Thu, 21 July 2005 18:49  |
 Dan Bourque
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
Hi all,
I've been having indexer-related problems for a while now, and I'm hoping
you can help. I'm using Eclispe 3.1 with CDT 3.0 RC2 under Linux.
I use my own project creation wizard to create our projects, since the
source code the project will contain already exists at a specific NFS
location, under ClearCase (source management) control, and is relatively
large. The NFS location in question doesn't allow me to declare its root
at Eclipse's workspace, so I must create a link to that location in my
project. I *think* this is what's causing my problems.
I've tried creating an Eclipse resource style link, i.e.
newProject.getFolder( "src" ).createLink( new Path( "/vob/cppsw" ), 0,
monitor ), as well as creating a symbolic link at the project's root
location that points to the source root, i.e. Runtime.getRuntime().exec(
"ln -s /vob/cppsw src, null, newProjectHandle.getLocation().toFile() ) ).
I then declare that folder as a SourceEntry.
However, regardless of how I specify my include directories, hyperlinking
never works. The C/C++ indexers are only complaining about a very few
unresolved includes (not related to the code I'm trying to navigate). The
only way I ever got hyperlinking to work with this setup was to add an
"external include path" pointing to /vob/cppsw, but in this case
hyperlinking opens an editor on a resource that is not considered to be a
part of my project, and therefore causes other problems.
Any suggestions? If it helps, I can VNC a session to better demonstrate
the problem.
Cheers,
-Dan.
PS: On a side note, I'll likely be giving a presentation at next year's
EclipseCON to show my work on temporal debugging, namely allowing users to
single-step & run a program forwards & backwards in time, hitting
breakpoints in reverse, showing advanced performance metrics, etc.
|
|
|
| Re: Hyperlinking (open declaration/definition) problems [message #149733 is a reply to message #149714] |
Thu, 21 July 2005 19:40  |
Dan Bourque
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
I should've mentioned, I also tried adding a container entry to all
discovered include paths & symbols, i.e. new ContainerEntry( new Path(
"org.eclipse.cdt.make.core.DISCOVERED_SCANNER_INFO" ), false ) at project
creation time, and therefore the Includes container gets populated with
everything needed (indexer doesn't complain about anything), but it still
gives me the same problem whereby hyperlinking to a forward declaration
opens an editor on a file it considers to be outside of the project. So
when I have the "Link with Editor" toggle on, it's not linked.
Regards,
-Dan.
Dan Bourque wrote:
> Hi all,
> I've been having indexer-related problems for a while now, and I'm hoping
> you can help. I'm using Eclispe 3.1 with CDT 3.0 RC2 under Linux.
> I use my own project creation wizard to create our projects, since the
> source code the project will contain already exists at a specific NFS
> location, under ClearCase (source management) control, and is relatively
> large. The NFS location in question doesn't allow me to declare its root
> at Eclipse's workspace, so I must create a link to that location in my
> project. I *think* this is what's causing my problems.
> I've tried creating an Eclipse resource style link, i.e.
> newProject.getFolder( "src" ).createLink( new Path( "/vob/cppsw" ), 0,
> monitor ), as well as creating a symbolic link at the project's root
> location that points to the source root, i.e. Runtime.getRuntime().exec(
> "ln -s /vob/cppsw src, null, newProjectHandle.getLocation().toFile() ) ).
> I then declare that folder as a SourceEntry.
> However, regardless of how I specify my include directories, hyperlinking
> never works. The C/C++ indexers are only complaining about a very few
> unresolved includes (not related to the code I'm trying to navigate). The
> only way I ever got hyperlinking to work with this setup was to add an
> "external include path" pointing to /vob/cppsw, but in this case
> hyperlinking opens an editor on a resource that is not considered to be a
> part of my project, and therefore causes other problems.
> Any suggestions? If it helps, I can VNC a session to better demonstrate
> the problem.
> Cheers,
> -Dan.
> PS: On a side note, I'll likely be giving a presentation at next year's
> EclipseCON to show my work on temporal debugging, namely allowing users to
> single-step & run a program forwards & backwards in time, hitting
> breakpoints in reverse, showing advanced performance metrics, etc.
|
|
|
| Re: Hyperlinking (open declaration/definition) problems [message #149749 is a reply to message #149733] |
Fri, 22 July 2005 02:46 |
John Camelon
Messages: 242
Registered: July 2009 |
Senior Member |
|
|
We've fixed quite a few linked-resource/folder defects regarding the
indexer, open include action, Open Declaration/Definition etc. for CDT RC3
(available soon).
Ref: Bugzilla defects 76043, 78354, 103697, 104532.
If you can try out whats in CVS HEAD right now you'll know if these fixes
help you with your problem.
Otherwise, you can wait for RC3 to be available later this month-ish.
Thanks
JC
"Dan Bourque" <dabourqu@cisco.com> wrote in message
news:b55a9fa206bc4eadae390f4fa1b8e2e3$1@www.eclipse.org...
> I should've mentioned, I also tried adding a container entry to all
> discovered include paths & symbols, i.e. new ContainerEntry( new Path(
> "org.eclipse.cdt.make.core.DISCOVERED_SCANNER_INFO" ), false ) at project
> creation time, and therefore the Includes container gets populated with
> everything needed (indexer doesn't complain about anything), but it still
> gives me the same problem whereby hyperlinking to a forward declaration
> opens an editor on a file it considers to be outside of the project. So
> when I have the "Link with Editor" toggle on, it's not linked.
>
> Regards,
> -Dan.
>
>
> Dan Bourque wrote:
>
> > Hi all,
>
> > I've been having indexer-related problems for a while now, and I'm
hoping
> > you can help. I'm using Eclispe 3.1 with CDT 3.0 RC2 under Linux.
>
> > I use my own project creation wizard to create our projects, since the
> > source code the project will contain already exists at a specific NFS
> > location, under ClearCase (source management) control, and is relatively
> > large. The NFS location in question doesn't allow me to declare its
root
> > at Eclipse's workspace, so I must create a link to that location in my
> > project. I *think* this is what's causing my problems.
>
> > I've tried creating an Eclipse resource style link, i.e.
> > newProject.getFolder( "src" ).createLink( new Path( "/vob/cppsw" ), 0,
> > monitor ), as well as creating a symbolic link at the project's root
> > location that points to the source root, i.e. Runtime.getRuntime().exec(
> > "ln -s /vob/cppsw src, null,
newProjectHandle.getLocation().toFile() ) ).
> > I then declare that folder as a SourceEntry.
>
> > However, regardless of how I specify my include directories,
hyperlinking
> > never works. The C/C++ indexers are only complaining about a very few
> > unresolved includes (not related to the code I'm trying to navigate).
The
> > only way I ever got hyperlinking to work with this setup was to add an
> > "external include path" pointing to /vob/cppsw, but in this case
> > hyperlinking opens an editor on a resource that is not considered to be
a
> > part of my project, and therefore causes other problems.
>
> > Any suggestions? If it helps, I can VNC a session to better demonstrate
> > the problem.
>
> > Cheers,
> > -Dan.
>
> > PS: On a side note, I'll likely be giving a presentation at next year's
> > EclipseCON to show my work on temporal debugging, namely allowing users
to
> > single-step & run a program forwards & backwards in time, hitting
> > breakpoints in reverse, showing advanced performance metrics, etc.
>
|
|
|
| Re: Hyperlinking (open declaration/definition) problems [message #149860 is a reply to message #149749] |
Fri, 22 July 2005 17:59 |
Dan Bourque
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
Thanks John,
That's my favorite kind of answer. I'll wait until RC3 comes out. Thanks
for the help.
Cheers,
-Dan.
PS: I know Bogdan works (or worked) on the indexers. Coincidentally, his
Dad, Serban, was my manager when I lived in Canada (working for Silicon
Access Networks, in Ottawa). Small world. I'm working for Cisco in
Silicon Valley, California now.
johnc wrote:
> We've fixed quite a few linked-resource/folder defects regarding the
> indexer, open include action, Open Declaration/Definition etc. for CDT RC3
> (available soon).
> Ref: Bugzilla defects 76043, 78354, 103697, 104532.
> If you can try out whats in CVS HEAD right now you'll know if these fixes
> help you with your problem.
> Otherwise, you can wait for RC3 to be available later this month-ish.
> Thanks
> JC
> "Dan Bourque" <dabourqu@cisco.com> wrote in message
> news:b55a9fa206bc4eadae390f4fa1b8e2e3$1@www.eclipse.org...
>> I should've mentioned, I also tried adding a container entry to all
>> discovered include paths & symbols, i.e. new ContainerEntry( new Path(
>> "org.eclipse.cdt.make.core.DISCOVERED_SCANNER_INFO" ), false ) at project
>> creation time, and therefore the Includes container gets populated with
>> everything needed (indexer doesn't complain about anything), but it still
>> gives me the same problem whereby hyperlinking to a forward declaration
>> opens an editor on a file it considers to be outside of the project. So
>> when I have the "Link with Editor" toggle on, it's not linked.
>>
>> Regards,
>> -Dan.
>>
>>
>> Dan Bourque wrote:
>>
>> > Hi all,
>>
>> > I've been having indexer-related problems for a while now, and I'm
> hoping
>> > you can help. I'm using Eclispe 3.1 with CDT 3.0 RC2 under Linux.
>>
>> > I use my own project creation wizard to create our projects, since the
>> > source code the project will contain already exists at a specific NFS
>> > location, under ClearCase (source management) control, and is relatively
>> > large. The NFS location in question doesn't allow me to declare its
> root
>> > at Eclipse's workspace, so I must create a link to that location in my
>> > project. I *think* this is what's causing my problems.
>>
>> > I've tried creating an Eclipse resource style link, i.e.
>> > newProject.getFolder( "src" ).createLink( new Path( "/vob/cppsw" ), 0,
>> > monitor ), as well as creating a symbolic link at the project's root
>> > location that points to the source root, i.e. Runtime.getRuntime().exec(
>> > "ln -s /vob/cppsw src, null,
> newProjectHandle.getLocation().toFile() ) ).
>> > I then declare that folder as a SourceEntry.
>>
>> > However, regardless of how I specify my include directories,
> hyperlinking
>> > never works. The C/C++ indexers are only complaining about a very few
>> > unresolved includes (not related to the code I'm trying to navigate).
> The
>> > only way I ever got hyperlinking to work with this setup was to add an
>> > "external include path" pointing to /vob/cppsw, but in this case
>> > hyperlinking opens an editor on a resource that is not considered to be
> a
>> > part of my project, and therefore causes other problems.
>>
>> > Any suggestions? If it helps, I can VNC a session to better demonstrate
>> > the problem.
>>
>> > Cheers,
>> > -Dan.
>>
>> > PS: On a side note, I'll likely be giving a presentation at next year's
>> > EclipseCON to show my work on temporal debugging, namely allowing users
> to
>> > single-step & run a program forwards & backwards in time, hitting
>> > breakpoints in reverse, showing advanced performance metrics, etc.
>>
|
|
|
| Re: Hyperlinking (open declaration/definition) problems [message #149945 is a reply to message #149860] |
Mon, 25 July 2005 16:57 |
Bogdan Gheorghe
Messages: 23
Registered: July 2009 |
Junior Member |
|
|
Hi Dan! Sorry I didn't get back to you earlier - I was off on vacation last
week. Like John mentioned, a bunch of fixes went into the stream after RC2 .
76043 sounds like your scenario (F3 opens external file instead of linked
resource). If you still have the same problem with RC3, please raise a bug
in bugzilla. All the best!
"Dan Bourque" <dabourqu@cisco.com> wrote in message
news:5d0c9da4a9ece8daef7e30a0509263e3$1@www.eclipse.org...
> Thanks John,
>
> That's my favorite kind of answer. I'll wait until RC3 comes out. Thanks
> for the help.
>
> Cheers,
> -Dan.
>
> PS: I know Bogdan works (or worked) on the indexers. Coincidentally, his
> Dad, Serban, was my manager when I lived in Canada (working for Silicon
> Access Networks, in Ottawa). Small world. I'm working for Cisco in
> Silicon Valley, California now.
>
>
> johnc wrote:
>
> > We've fixed quite a few linked-resource/folder defects regarding the
> > indexer, open include action, Open Declaration/Definition etc. for CDT
RC3
> > (available soon).
> > Ref: Bugzilla defects 76043, 78354, 103697, 104532.
> > If you can try out whats in CVS HEAD right now you'll know if these
fixes
> > help you with your problem.
> > Otherwise, you can wait for RC3 to be available later this month-ish.
>
> > Thanks
> > JC
>
> > "Dan Bourque" <dabourqu@cisco.com> wrote in message
> > news:b55a9fa206bc4eadae390f4fa1b8e2e3$1@www.eclipse.org...
> >> I should've mentioned, I also tried adding a container entry to all
> >> discovered include paths & symbols, i.e. new ContainerEntry( new Path(
> >> "org.eclipse.cdt.make.core.DISCOVERED_SCANNER_INFO" ), false ) at
project
> >> creation time, and therefore the Includes container gets populated with
> >> everything needed (indexer doesn't complain about anything), but it
still
> >> gives me the same problem whereby hyperlinking to a forward declaration
> >> opens an editor on a file it considers to be outside of the project.
So
> >> when I have the "Link with Editor" toggle on, it's not linked.
> >>
> >> Regards,
> >> -Dan.
> >>
> >>
> >> Dan Bourque wrote:
> >>
> >> > Hi all,
> >>
> >> > I've been having indexer-related problems for a while now, and I'm
> > hoping
> >> > you can help. I'm using Eclispe 3.1 with CDT 3.0 RC2 under Linux.
> >>
> >> > I use my own project creation wizard to create our projects, since
the
> >> > source code the project will contain already exists at a specific NFS
> >> > location, under ClearCase (source management) control, and is
relatively
> >> > large. The NFS location in question doesn't allow me to declare its
> > root
> >> > at Eclipse's workspace, so I must create a link to that location in
my
> >> > project. I *think* this is what's causing my problems.
> >>
> >> > I've tried creating an Eclipse resource style link, i.e.
> >> > newProject.getFolder( "src" ).createLink( new Path( "/vob/cppsw" ),
0,
> >> > monitor ), as well as creating a symbolic link at the project's root
> >> > location that points to the source root, i.e.
Runtime.getRuntime().exec(
> >> > "ln -s /vob/cppsw src, null,
> > newProjectHandle.getLocation().toFile() ) ).
> >> > I then declare that folder as a SourceEntry.
> >>
> >> > However, regardless of how I specify my include directories,
> > hyperlinking
> >> > never works. The C/C++ indexers are only complaining about a very
few
> >> > unresolved includes (not related to the code I'm trying to navigate).
> > The
> >> > only way I ever got hyperlinking to work with this setup was to add
an
> >> > "external include path" pointing to /vob/cppsw, but in this case
> >> > hyperlinking opens an editor on a resource that is not considered to
be
> > a
> >> > part of my project, and therefore causes other problems.
> >>
> >> > Any suggestions? If it helps, I can VNC a session to better
demonstrate
> >> > the problem.
> >>
> >> > Cheers,
> >> > -Dan.
> >>
> >> > PS: On a side note, I'll likely be giving a presentation at next
year's
> >> > EclipseCON to show my work on temporal debugging, namely allowing
users
> > to
> >> > single-step & run a program forwards & backwards in time, hitting
> >> > breakpoints in reverse, showing advanced performance metrics, etc.
> >>
>
|
|
|
Goto Forum:
Current Time: Sat Jul 27 19:24:05 GMT 2024
Powered by FUDForum. Page generated in 0.03706 seconds |
] 
Search
Help
Register
Login
Home
