| commit | c63d9ecbe5fcb5716a0be21d8fc781d7aa5bbc30 | [log] [tgz] |
|---|---|---|
| author | pcloudy <pcloudy@google.com> | Tue Jan 04 02:38:47 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 04 02:40:19 2022 -0800 |
| tree | 9d8e0a96937eaa536e6ab4f96c0cf4b20297b19f | |
| parent | 2edab739e1f61fe8813230b03396ca46f0790089 [diff] |
Automated rollback of commit bfdfa6ebfd21b388f1c91f512291c848e1a92a96. *** Reason for rollback *** Due to https://github.com/bazelbuild/bazel/issues/14500 *** Original change description *** Update find runfiles manifest file logic This pull request updates the `FindManifestFileImpl` function to look for the runfiles manifest file of the binary first. If it is not found, it can use the manifest file specified in the environment variables `RUNFILES_MANIFEST_FILE` if it exists. The same logic is applied in `runfiles_src.cc` to find runfiles manifest file / directory of cc binaries. This is done to avoid using the manifest file... *** PiperOrigin-RevId: 419548921
{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
