| commit | 3badca3f7e539e4b56fd5c502233c03b9934b813 | [log] [tgz] |
|---|---|---|
| author | Ed Schouten <eschouten@apple.com> | Tue Jan 04 20:15:17 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 04 20:16:54 2022 -0800 |
| tree | ae7deba1046f058d0805e4d79ea260fb6fb51e2f | |
| parent | 820c8872a55f4d269a4e3d9b05a7a473b0ccadf7 [diff] |
Make --nobuild_runfiles_links work in combination with --run_under When both of these flags are provided, we must make sure that a "bazel run" forcefully instantiates the runfiles directories both for the target to run, and the --run_under target. Right now it only ensures this for the former, which causes execution errors along the lines of: Cannot find .runfiles directory for /some/path This code alters the existing code block that ensures that runfiles exist to loop over the entire set of targets. We do need to capture the path of the runfiles directory of the target to run, as it may need be used as the working directory later on. Closes #14471. PiperOrigin-RevId: 419734836
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
