diff options
| author |  lberki <lberki@google.com> | 2018-02-13 05:13:31 -0800 |
|---|---|---|
| committer |  Copybara-Service <copybara-piper@google.com> | 2018-02-13 05:15:12 -0800 |
| commit | 3bd6663e3644bf22606860bf2e594a07425bcbc1 (patch) | |
| tree | c050f3a57b6848e042de40054883978b604879a7 /src/main/java/com/google/devtools/build/lib/rules/cpp/CppConfigurationLoader.java | |
| parent | 04757dba0174d22c0a695a7ed5fe511fd13df008 (diff) | |
Add the BUILD_WORKSPACE_DIRECTORY and BUILD_WORKING_DIRECTORY variables to "blaze run --direct_run" so that the called binary knows about the working directory the client was called from.
Its cwd is its runfiles directory and if not for the fact that we have to convey *two* directories to it, I'd have considered changing that. As it is, however, we can't convey two directories with the cwd of the binary so we have to use environment variables.
RELNOTES[NEW]: "blaze run --direct_run" now exports the BUILD_{WORKSPACE,WORKING}_DIRECTORY variables to tell the binary about the cwd of the client and the workspace root.
PiperOrigin-RevId: 185515884
Diffstat (limited to 'src/main/java/com/google/devtools/build/lib/rules/cpp/CppConfigurationLoader.java')
0 files changed, 0 insertions, 0 deletions