| commit | 0f6d0d839381e9ccee5fd8857c449d6d76ba8714 | [log] [tgz] |
|---|---|---|
| author | Googler <ilist@google.com> | Thu Sep 12 01:58:37 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Sep 12 02:00:02 2024 -0700 |
| tree | eea23844ac9dcc3978dede0cb5458ce071aef4f8 | |
| parent | be9668d36f46949351973741d63178119a46ed51 [diff] |
Implement legacy_symbols In the repositories that don't have autoloads we also expose native.legacy_symbols. Those can be used to fallback to the native symbol, whenever it's still available in Bazel. Fallback using a top-level symbol doesn't work, because BzlCompileFunction would throw an error when it's mentioned. legacy_symbols aren't available when autoloads are not enabled. The feature is intended to be used with bazel_features repository, which can correctly report native symbols on all versions of Bazel. PiperOrigin-RevId: 673741927 Change-Id: I2334030d70cbb944b92784e32a184841ea238d51
{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
