aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/main/java/com/google/devtools/build/lib/analysis/config
diff options
context:
space:
mode:
authorGravatar Googler <noreply@google.com>2017-08-17 05:40:27 +0200
committerGravatar Irina Iancu <elenairina@google.com>2017-08-17 09:54:45 +0200
commitab38960b9f34b965352d953afc00b918a97966a3 (patch)
tree35ec33254ef4033482bfc901a26a5c25bedaee58 /src/main/java/com/google/devtools/build/lib/analysis/config
parent5e65c9828f424b6b0214b984b5d38c9cfc1c746f (diff)
Honor --nobuild_runfile_links for non-tests, and propagate it to the
host configuration. I think the comment I'm deleting is misleading. PAR file construction already has special handling of the input manifest, and host tools do get their runfiles when executed remotely. They don't get them for local execution, but users who care about that don't need to pass the non-default --nobuild_runfile_links option. RELNOTES: None. PiperOrigin-RevId: 165535870
Diffstat (limited to 'src/main/java/com/google/devtools/build/lib/analysis/config')
-rw-r--r--src/main/java/com/google/devtools/build/lib/analysis/config/BuildConfiguration.java5
1 files changed, 1 insertions, 4 deletions
diff --git a/src/main/java/com/google/devtools/build/lib/analysis/config/BuildConfiguration.java b/src/main/java/com/google/devtools/build/lib/analysis/config/BuildConfiguration.java
index db9649d495..7dcb00cd9b 100644
--- a/src/main/java/com/google/devtools/build/lib/analysis/config/BuildConfiguration.java
+++ b/src/main/java/com/google/devtools/build/lib/analysis/config/BuildConfiguration.java
@@ -1062,10 +1062,7 @@ public final class BuildConfiguration implements BuildEvent {
}
// === Runfiles ===
- // Ideally we could force this the other way, and skip runfiles construction
- // for host tools which are never run locally, but that's probably a very
- // small optimization.
- host.buildRunfiles = true;
+ host.buildRunfiles = buildRunfiles;
// === Linkstamping ===
// Disable all link stamping for the host configuration, to improve action