Re: How to determine the standard C/C++ include paths?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alex Flint <alex.flint@xxxxxxxxx> writes:

> I was wondering how, on a given system, I can determine which include
> paths are automatically searched by gcc (and similarly for g++ when
> compiling c++ sources). That is, which paths are _not_ searched when
> using -nostdinc (and similarly for -nostdinc++)?
>
> The reason is that I need to supply these paths to the Eclipse source
> indexer so that it can resolve all my includes and do pretty context
> assist etc.

If you use the -v option when running the compiler, it will show you,
among other things, the exact set of directories that it is searching.

Ian

[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux