C++ Logo


Advanced search

Re: [Tooling] [isocpp-modules] Dependency information for module-aware build tools

From: Ben Boeckel <ben.boeckel_at_[hidden]>
Date: Wed, 6 Mar 2019 15:13:26 -0500
On Wed, Mar 06, 2019 at 15:01:40 -0500, Mathias Stearn wrote:
> On Wed, Mar 6, 2019 at 10:18 AM Nathan Sidwell <nathan_at_[hidden]> wrote:
> > Yes, a BMI is required for a header import. Textually including the
> > header import's original header file is not equivalent.
> >
> It won't be required for the scan stage will it? If it is, there is a
> bootstrapping problem because there is no good way to figure out which
> order to build the header-unit BMIs in if they import other header-units.
> I've been assuming that the scan stage will be able to just temporarily
> mask off the defines and replace them with the correct ones for the
> header-unit while scanning a file, so that scanning has no generated
> dependencies.

This was mentioned in another subthread ending here (relevant context is
in the message):


the start of it is:

    Message-Id: <20190305162900.GE2154_at_[hidden]>


Received on 2019-03-06 21:13:30