C++ Logo


Advanced search

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

From: Ben Boeckel <ben.boeckel_at_[hidden]>
Date: Tue, 5 Mar 2019 11:29:00 -0500
On Tue, Mar 05, 2019 at 16:14:19 +0000, Gabriel Dos Reis wrote:
> Header units name (in source code) exactly a header or a header file
> that can be found by #include. The path to the actual artifact that
> is loaded is different, since it is a BMI.

So even scanning might need BMIs generated? That might be a problem, but
CMake (and other tools) can probably ensure that header unit generation
get into the build graph properly[1], but this is unlikely to be optimal
considering what I was hoping CMake would be able to do with
unreferenced header unit modules (not making BMIs for them at all).

Is it feasible for scanning to not do that and instead load it as if it
were `#include` and dropping non-exported macros at the end of the


[1]Though generating module map files for the scan step too…not so

Received on 2019-03-05 17:29:11