public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/104500] New: Document directory layout for installed C++ headers
@ 2022-02-11 11:59 redi at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: redi at gcc dot gnu.org @ 2022-02-11 11:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104500
Bug ID: 104500
Summary: Document directory layout for installed C++ headers
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Keywords: documentation
Severity: minor
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
https://gcc.gnu.org/onlinedocs/libstdc++/manual/source_organization.html
describes the directory layout in the source tree, but we have nothing
describing the post-install tree.
Draft:
Libstdc++ headers are always split across three directories:
$prefix/include/c++/$version: Most headers are here, and are
target-independent.
$prefix/include/c++/$version/$triplet: target-specific headers such as
bits/c++config.h, CPU-specific atomics (predating __atomic built-ins and
libatomic), and headers that depend on the build-time GCC config options like
the choice of thread model, locale backend, allocator backend, etc.
$prefix/include/c++/$version/backward: <strstream> and legacy headers like
<hash_map>.
The second one will be modified by the multilib options, so on x86_64 -m32 will
use $prefix/include/c++/$version/$triplet/32 instead.
In all cases, $version might be X.Y.Z or just X if GCC was configured with
--with-gcc-major-version-only
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-02-11 11:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-11 11:59 [Bug libstdc++/104500] New: Document directory layout for installed C++ headers redi at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).