On Tue, Oct 29, 2024 at 17:59:17 +0200, Boris Kolpackov wrote:
> You write two separate databases, one for debug and one for release?
> Maybe this is impossible/difficult in CMake, but not "generally".

Sure, but which one "is" `compile_commands.json`? AFAIK, the static file
name is a big part of the It Just Works™ of compile commands.

> The "consuming" TU's command line will include module references
> (e.g., Clang's -fmodule-file options, MSVC's /reference, etc). From
> that one should be able to determine which modules are visible to
> each TU, no?

CMake only fills in the modules that are actually used as of the last
build; the available-to-use list is not available on the command line.

--Ben