[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cdt-dev] How to Set Up C/C++ #include <...> vs. #include "..."Paths in Eclipse?
|
Did Jens reply answer your
question?
Subs <
dmsubs@xxxxxxxxxxxxx>
wrote...
> RTFM for gcc? It's not a CDT question...
> The
option you are looking for is -isystem which you will have to add as
> a
miscellaneous option.
Well, and I could say to you, RTFQ ("Question"):
I specifically said that I was asking in the context of the Eclipse C/C++
Indexer, i.e. the Fast Indexer, so I would assume that gcc options are
irrelevant -- I'm not trying to correct a compilation issue, I'm trying to
correct an Eclipse indexing issue.
--- Begin Message ---
Title: RE: [cdt-dev] How to Set Up C/C++ #include <...> vs. #include"..."Paths in Eclipse?
Hi Tom,
The Project properties -> C/C++ General -> Paths and Symbols should be the place to go.
They are responsible for the -I options in the gcc command line. The gcc, as the indexer (right?) applies the same include paths to both #include <file> and #include "file". The only difference is, that before searching for in the list of include paths, a C preprocessor checks that local directory if #include "file" is used.
Did you try the "paths ans symbols" setting?
Greetings, Jens E.
Jens Elmenthaler
Platform & Components Lab
SW Designer R&D
Verigy Germany GmbH, Herrenberger Str. 130, 71034 Böblingen
Sitz der Gesellschaft: Böblingen - Amtsgericht Böblingen HRB 6167
WEEE-Reg.-Nr. DE 16968742
Geschäftsführer: Hans-Jürgen Wagner, Dietmar Höller
Tel: +49 7031 4357-119
jens.elmenthaler@xxxxxxxxxx
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Subs
Sent: Wednesday, September 17, 2008 08:31
To: CDT General developers list.
Subject: Re: [cdt-dev] How to Set Up C/C++ #include <...> vs. #include "..."Paths in Eclipse?
RTFM for gcc? It's not a CDT question...
The option you are looking for is -isystem which you will have to add as
a miscellaneous option.
Tom Chappell wrote:
> I have an Eclipse C++ Makefile-type project, trying to use Eclipse to
> view some existing C/C++ source code, using the Linux GCC tool chain.
>
> The project's source files have some lines like this, using the <system>
> include-type:
>
> #include <somefile.h>
>
> ...vs. the "project" include type:
>
> #include "somefile.h"
>
> My problem is that some of the files that are referenced by the #include
> <somefile.h> lines are not part of the standard Linux GCC, so, among
> other things, the C/C++ indexer is failing to index them. How can I
> teach Eclipse, and its C/C++ indexer, some additional paths to search
> for to find "system"-type files via #include <somefile.h>?
>
> Of course, there is the [Project Properties, C/C++ General, Paths and
> Symbols], but these seem only to set up the paths for the #include
> "somefile.h"-type includes. That's perfectly legitimate, but I expect
> there to be a way, somehow, to augment the #include <somefile.h>-type
> include paths. I am *particularly* interested in doing this for the the
> benefit of the indexer.
>
> But how?
>
> Thanks,
> -Tom
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
--
Subs
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
--- End Message ---