They’re stuffed under
compile_commands.json should have it there, but there is an issue for that.
I expect there to be a per-target
modules_commands.json that gets generated during the build, yes. It cannot be for the entire build because then running part of it will not update the overall file. A mechanism to merge all files for complete builds (though
EXCLUDE_FROM_ALL throws a wrench in here) could be provided though that works for the
all target at least.