gccint: Header Dirs
1
1 22 Standard Header File Directories
1 ***********************************
1
1 'GCC_INCLUDE_DIR' means the same thing for native and cross. It is
1 where GCC stores its private include files, and also where GCC stores
1 the fixed include files. A cross compiled GCC runs 'fixincludes' on the
1 header files in '$(tooldir)/include'. (If the cross compilation header
1 files need to be fixed, they must be installed before GCC is built. If
1 the cross compilation header files are already suitable for GCC, nothing
1 special need be done).
1
1 'GPLUSPLUS_INCLUDE_DIR' means the same thing for native and cross. It
1 is where 'g++' looks first for header files. The C++ library installs
1 only target independent header files in that directory.
1
1 'LOCAL_INCLUDE_DIR' is used only by native compilers. GCC doesn't
1 install anything there. It is normally '/usr/local/include'. This is
1 where local additions to a packaged system should place header files.
1
1 'CROSS_INCLUDE_DIR' is used only by cross compilers. GCC doesn't
1 install anything there.
1
1 'TOOL_INCLUDE_DIR' is used for both native and cross compilers. It is
1 the place for other packages to install header files that GCC will use.
1 For a cross-compiler, this is the equivalent of '/usr/include'. When
1 you build a cross-compiler, 'fixincludes' processes any header files in
1 this directory.
1