| Setting include and library paths [message #197076] |
Fri, 13 July 2007 18:32  |
Eclipse User |
|
|
|
Originally posted by: usenet.aristeia.com
I'm new to Eclipse, CDT, and IDEs. In playing around with simple projects, one
issue that has arisen is how to best deal with search paths for includes and
link libraries. I'm running Eclipse Europa on Windows XP.
One option is to set the paths in environment variables, as Eclipse seems to use
the environment that is set at the time Eclipse is invoked. This has the
advantage that all projects see changes to the search paths each time I start
Eclipse. It has the disadvantage that later changes to the search paths might
cause some project builds to break without any obvious reason, since nothing
within Eclipse will have changed.
Another option is to explicitly specify the search paths for each project, but
this has the drawback that it involves a lot of redundant work, both when a new
project is created (to enter search path information that is already present in
other projects) and when the search paths change. This could be mitigated if
there were a way to easily copy project settings from one project to another,
but I don't know if such an easy mechanism exists. Does one?
Thanks for any advice on how to handle this.
Scott
|
|
|
| Re: Setting include and library paths [message #197086 is a reply to message #197076] |
Fri, 13 July 2007 20:08  |
| Eclipse User |
|
|
|
Scott Meyers wrote:
> I'm new to Eclipse, CDT, and IDEs. In playing around with simple
> projects, one issue that has arisen is how to best deal with search
> paths for includes and link libraries. I'm running Eclipse Europa on
> Windows XP.
>
> One option is to set the paths in environment variables, as Eclipse
> seems to use the environment that is set at the time Eclipse is
> invoked. This has the advantage that all projects see changes to the
> search paths each time I start Eclipse. It has the disadvantage that
> later changes to the search paths might cause some project builds to
> break without any obvious reason, since nothing within Eclipse will have
> changed.
>
> Another option is to explicitly specify the search paths for each
> project, but this has the drawback that it involves a lot of redundant
> work, both when a new project is created (to enter search path
> information that is already present in other projects) and when the
> search paths change. This could be mitigated if there were a way to
> easily copy project settings from one project to another, but I don't
> know if such an easy mechanism exists. Does one?
>
> Thanks for any advice on how to handle this.
>
> Scott
Currently the environment variable approach is probably the best. There
is currently no good way to clone the paths from project to project.
This has been asked for by someone else recently... it probably merits
an enhancement request in Bugzilla.
===========================
Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt
|
|
|
Powered by
FUDForum. Page generated in 0.02440 seconds
Home