P2898 R1 Build System Requirements for Importable Headers

[wg21bot]

P2898R0 Importable Headers are Not Universally Implementable (Daniel Ruoso)

[Bigcheese]

Identification of importable headers will require at least
metadata that is co-located with the headers as found by the
regular source inclusion search process. That process will also
need to support an "overlay" to allow the user to specify headers
they don't own as importable.

SF	F	N	A	SA
7	6	1	0	0

Header units have no "Local Preprocessor Arguments". Any argument
that is required to consume an importable header becomes a part
of the global preprocessor arguments.

SF	F	N	A	SA
10	2	2	0	0

The dependency scanning process needs both the command line for
the translation unit being scanned and the baseline command line
for translating header units to emulate the import of header
units.

SF	F	N	A	SA
6	6	2	0	0

[wg21bot]

P2898R1 Build System Requirements for Importable Headers (Daniel Ruoso)

[ruoso]

cplusplus/modules-ecosystem-tr#26 has the changes to the draft module ecosystem TR for this paper. Once that's merged, this can be closed.

[Bigcheese]

This has been merged into the modules ecosystem tr.