|Re: Removing default include paths [message #211228]
||Thu, 06 March 2008 19:24
Originally posted by: merks.ca.ibm.com|
I'll redirect your question to the CDT newsgroup by adding it to the
"to" list of this reply.
> I'm new to Eclipse, running 3.3.2 with CDT 4.0.1 on Linux (Fedora Core
> 6), using GNU C/C++ tools.
> How can I control the default include paths that appear when I create
> a project? When I create the supplied Hello World (C++) project, it
> pulls in an "Includes" tree of apparently every .h file it finds under
> /usr. I'd like to be able to remove the paths that are not needed.
> This is important, as I will be compiling using an older version of
> g++. I have multiple GNU tools installed. I think I know how to
> specify the compiler on a per-project basis, but I don't know how to
> ensure that the project seeks the correct include paths.
|Re: Removing default include paths [message #211261 is a reply to message #211228]
||Thu, 06 March 2008 21:57
Originally posted by: gary.thorburn.hds.com|
I think I can now answer my own question, thanks in part to the 24 Feb
discussion between Nikosch and Tracy Miranda in the eclipse.tools.cdt
thread. There are two separate issues here:
1) There may in fact be no conflict: g++ / gcc will find the paths
matching its version, if the tools were built correctly and their include
directories have not been molested. I verified this by creating two hello
world projects, assigning different compilers to each. (My system has two
versions installed.) Then I renamed the iostream header file in each path
temporarily, and the proper build for the renamed path failed.
2) Nevertheless, there still might be occasions when deleting a default
path might be desirable. Bug 206372
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=206372) acknowledges an
issue here. A workaround is mentioned in the writeup for this bug which
involves moving, deleting, or editing (depending on your tolerance for
Powered by FUDForum
. Page generated in 0.02238 seconds