If dynamic configurations are turned on, ruleclass configuration transitions

apply on the top level.

--
PiperOrigin-RevId: 148155171
MOS_MIGRATED_REVID=148155171

1 files changed, 12 insertions, 1 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/analysis/BuildView.java b/src/main/java/com/google/devtools/build/lib/analysis/BuildView.java
index 1f12d2cc0b..015fea9071 100644
--- a/src/main/java/com/google/devtools/build/lib/analysis/BuildView.java
+++ b/src/main/java/com/google/devtools/build/lib/analysis/BuildView.java
@@ -850,11 +850,22 @@ public class BuildView {
 
     for (TargetAndConfiguration targetAndConfig : inputs) {
       labelsToTargets.put(targetAndConfig.getLabel(), targetAndConfig.getTarget());
+
+      Attribute.Transition ruleclassTransition = null;
+      if (targetAndConfig.getTarget().getAssociatedRule() != null) {
+        ruleclassTransition = targetAndConfig
+            .getTarget()
+            .getAssociatedRule()
+            .getRuleClassObject()
+            .getTransition();
+      }
       if (targetAndConfig.getConfiguration() != null) {
         asDeps.put(targetAndConfig.getConfiguration(),
             Dependency.withTransitionAndAspects(
                 targetAndConfig.getLabel(),
-                Attribute.ConfigurationTransition.NONE,
+                ruleclassTransition == null
+                  ? Attribute.ConfigurationTransition.NONE
+                  : ruleclassTransition,
                 // TODO(bazel-team): support top-level aspects
                 AspectCollection.EMPTY));
       }