Add SpawnInputExpander helper class to arrange runfiles for spawn strategies

This new class is a combination of SpawnHelper and our internal code; the
plan is to migrate all spawn strategies to the new class. The strict flag
should be enabled by default, but that's a breaking change, so we need to do
it later.

- Use it in SandboxStrategy.
- Add ActionInput.getExecPath to return a PathFragment; this avoids lots of
  back and forth between path fragments and strings.

This is a step towards #1593.

--
PiperOrigin-RevId: 150427021
MOS_MIGRATED_REVID=150427021

1 files changed, 8 insertions, 1 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/actions/ActionInput.java b/src/main/java/com/google/devtools/build/lib/actions/ActionInput.java
index 6fa1df2cbc..90d4c5ff00 100644
--- a/src/main/java/com/google/devtools/build/lib/actions/ActionInput.java
+++ b/src/main/java/com/google/devtools/build/lib/actions/ActionInput.java
@@ -14,6 +14,8 @@
 
 package com.google.devtools.build.lib.actions;
 
+import com.google.devtools.build.lib.vfs.PathFragment;
+
 /**
  * Represents an input file to a build action, with an appropriate relative path and digest
  * value.
@@ -35,5 +37,10 @@ public interface ActionInput {
   /**
    * @return the relative path to the input file.
    */
-  public String getExecPathString();
+  String getExecPathString();
+
+  /**
+   * @return the relative path to the input file.
+   */
+  PathFragment getExecPath();
 }