| Open Declaration/Definition [message #153713] |
Mon, 12 September 2005 15:05  |
Eclipse User |
|
|
|
Originally posted by: Steven_G_Stetka.raytheon.com
It seems that the Open Declaration/Open Definition features of CDT only
work if the source/header files are all in the same sub-directory within
the source code directory. Is there a way to customize these features so
that the tools search up and across directories? For example if I have
code in project/widgets/widget1/src, I'd like to be able to find
definitions/declarations in project/inc, project/src, project/widgets/inc,
project/widgets/src, project/widgets/widget1/inc, and
project/widgets/widget1/src where project is the root source directory.
|
|
|
|
| Re: Open Declaration/Definition [message #154053 is a reply to message #154013] |
Wed, 14 September 2005 19:30  |
 Randy D. Smith
Messages: 394
Registered: July 2009 |
Senior Member |
|
|
Might I suggest then that you post a follow-up to your original message that
explains exactly what you discovered? I'm serious! The fact that you ran
into something, posted a question, kept digging, and found a solution
implies you have knowledge that others might find useful. Follow "the open
source way" and share your knowledge with the rest of us! That way, when
someone does a search on some key part of the original problem (e.g., "open
definition declaration") they'll find your solution neatly packaged for
them.
Interestingly enough, I started to post the above purely in reaction to your
follow-up message enclosed below. Then I looked back at the original (that
I'd seen but forgotten a couple of days ago), and realized *I* had had the
same problem yesterday! However, being less persistent than you :-), and
actually only using CDT at that time to browse a chunk of code I was looking
at but not doing anything else with, I just passed off the "inconsistency"
in being able to see definitions as "something" that was below my radar at
the time, and ignored the problem. Now I know *why* I was seeing what I was
seeing... but it would be nice to know the workaround without have to do the
work myself (lazy software engineer that I am).
So please, share your knowledge with us!
--
RDS
"Steve Stetka" <Steven_G_Stetka@raytheon.com> wrote in message
news:6320c157c4e3b9ad1da75ba6f8efb047$1@www.eclipse.org...
>I have "discovered" how to make this happen.
>
|
|
|
| Re: Open Declaration/Definition [message #154565 is a reply to message #154053] |
Fri, 16 September 2005 19:00 |
| Eclipse User |
|
|
|
Originally posted by: Steven_G_Stetka.raytheon.com
I basically went through the CDT user's guide and found that after you
build, CDT will discover include paths. I don't have Eclipse fully
configured with a builder/compiler; however, I found that you can manually
specify include paths by going into the project properties, selecting
"C/C++ Include Paths and Symbols", and selecting either "Add External
Include Path" or "Add Include Path from Workspace". After that, F3 and
Shift F3 worked like a charm. Be sure to look at the CDT user's guide to
avoid some pitfalls they talk about.
|
|
|
Powered by
FUDForum. Page generated in 0.04308 seconds
] 
Search
Help
Register
Login
Home
