Add an experimental option to disable .d-file scanning for modular builds. When

building with C++ modules, .d file scanning is not effective as Clang (only
compiler supporting Bazel's version of C++ modules) reads all of the files
passed in anyway.

This is not meant to be activated yet, but for running experiments.

RELNOTES: None.
PiperOrigin-RevId: 203459168

1 files changed, 4 insertions, 0 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/rules/cpp/CppConfiguration.java b/src/main/java/com/google/devtools/build/lib/rules/cpp/CppConfiguration.java
index 523b8fecbf..376a88f688 100644
--- a/src/main/java/com/google/devtools/build/lib/rules/cpp/CppConfiguration.java
+++ b/src/main/java/com/google/devtools/build/lib/rules/cpp/CppConfiguration.java
@@ -937,6 +937,10 @@ public final class CppConfiguration extends BuildConfiguration.Fragment
     return cppOptions.pruneCppInputDiscovery;
   }
 
+  public boolean getNoDotdScanningWithModules() {
+    return cppOptions.noDotdScanningWithModules;
+  }
+
   public boolean getParseHeadersVerifiesModules() {
     return cppOptions.parseHeadersVerifiesModules;
   }