| 1 |
@c Copyright (C) 1988-2025 Free Software Foundation, Inc. |
| 2 |
@c This is part of the GCC manual. |
| 3 |
@c For copying conditions, see the file gcc.texi. |
| 4 |
|
| 5 |
@node Header Dirs |
| 6 |
@chapter Standard Header File Directories |
| 7 |
|
| 8 |
@code{GCC_INCLUDE_DIR} means the same thing for native and cross. It is |
| 9 |
where GCC stores its private include files, and also where GCC |
| 10 |
stores the fixed include files. A cross compiled GCC runs |
| 11 |
@code{fixincludes} on the header files in @file{$(tooldir)/include}. |
| 12 |
(If the cross compilation header files need to be fixed, they must be |
| 13 |
installed before GCC is built. If the cross compilation header files |
| 14 |
are already suitable for GCC, nothing special need be done). |
| 15 |
|
| 16 |
@code{GPLUSPLUS_INCLUDE_DIR} means the same thing for native and cross. It |
| 17 |
is where @command{g++} looks first for header files. The C++ library |
| 18 |
installs only target independent header files in that directory. |
| 19 |
|
| 20 |
@code{LOCAL_INCLUDE_DIR} is used only by native compilers. GCC |
| 21 |
doesn't install anything there. It is normally |
| 22 |
@file{/usr/local/include}. This is where local additions to a packaged |
| 23 |
system should place header files. |
| 24 |
|
| 25 |
@code{CROSS_INCLUDE_DIR} is used only by cross compilers. GCC |
| 26 |
doesn't install anything there. |
| 27 |
|
| 28 |
@code{TOOL_INCLUDE_DIR} is used for both native and cross compilers. It |
| 29 |
is the place for other packages to install header files that GCC will |
| 30 |
use. For a cross-compiler, this is the equivalent of |
| 31 |
@file{/usr/include}. When you build a cross-compiler, |
| 32 |
@code{fixincludes} processes any header files in this directory. |