| Project properties -> paths and symbols [message #204760] |
Tue, 13 November 2007 04:41  |
Eclipse User |
|
|
|
Originally posted by: mba.cosmigo.ru
Hello,
I've been wondering for a while, what is the meaning of tabs under
Project properties -> C/C++ General -> Paths and symbols?
I can think out meaning for a few of them, but still there are lots of
questions:
* Includes - here one should list all the locations of external headers
which should be accessible via #include <..> command. Is it so? Is it
used from managed build or for indexer? Does one have to explicitly add
there all subdirectories or just a top dir is enough? What's about
different languages here?
* Symbols - declaring external preprocessor defines?
* Libraries - ?
* Library paths - ?
Why having two tabs? Used only for managed build? Does something with
parser?
* Source location - ???
* Output location - ???
No idea at all how this should be used.
* References - seems to show what projects are referenced but current
project. I've been thinking that marking project as referenced would add
things it exports (listed in Export settings section) to my current
project, but this does not happen. What is the meaning of
C/C++ General -> Export settings??
Can someone clarify this issues. We are mostly interested in making
indexer working better with our project, but any other information would
be appreciated.
--
Best regards
Mikhail Barg
ICQ: 132560784
|
|
|
|
|
|
|
|
|
|
| Re: Project properties -> paths and symbols [message #206255 is a reply to message #206232] |
Fri, 07 December 2007 12:25  |
| Eclipse User |
|
|
|
Originally posted by: raimund.berger.invalid.dot.com
aegges@web.de (Axel Mueller) writes:
> Raimund wrote:
>
>> aegges@web.de (Axel Mueller) writes:
>
>>>> * References - seems to show what projects are referenced but
>>>> current project.
>>> Here you should list e.g. projects that contain self-build libraries
>>> that are needed to link your application. Every project listed here
>>> will be build *before* the actual project.
>
>> References are a feature I didn't find that well documented, given I
>> didn't miss something.
>
>> Strictly speaking they just seem to enforce project build order,
>> right?
> Not quite. They enforce that referenced projects are build as well if
> you build the current project. The build order is usually
> alphabetical. But you can change the build order in Preferences.
If you had said "built before" instead of "built as well" that
would've been what I basically understood, i.e. references determining
build order in the sense of walking up a (hopefully acyclic) directed
build dependency graph.
I assume that's what you meant anyway.
What I was wondering is whether references might create other,
"hidden" dependencies, like on the indexing. The term is just that
vague.
I take your reply as a "no", though. Implying that references are all
just about the build process.
Thanks, Raimund.
|
|
|
Powered by
FUDForum. Page generated in 0.25098 seconds
Home