fbd1528f02
`@AutoCodec(autoRegister=false)` will cause the generated codec to not auto-register -- so that, for example, a customized codec will take precedence and still make use of the generated codec. PiperOrigin-RevId: 811141276 Change-Id: I6cf08a8c794cbcc6341335118f1a208b9bd7fb99 |
||
|---|---|---|
| .bazelci | ||
| .github | ||
| examples | ||
| scripts | ||
| site | ||
| src | ||
| third_party | ||
| tools | ||
| .bazelrc | ||
| .bazelversion | ||
| .gitattributes | ||
| .gitignore | ||
| AUTHORS | ||
| bazel_downloader.cfg | ||
| BUILD | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CODEOWNERS | ||
| combine_distfiles.py | ||
| combine_distfiles_to_tar.sh | ||
| compile.sh | ||
| CONTRIBUTING.md | ||
| CONTRIBUTORS | ||
| distdir.bzl | ||
| extensions.bzl | ||
| LICENSE | ||
| maven_install.json | ||
| MODULE.bazel | ||
| MODULE.bazel.lock | ||
| README.md | ||
| repositories.bzl | ||
| requirements.txt | ||
| SECURITY.md | ||
Bazel
{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.
Getting Started
-
Follow our tutorials:
Documentation
- Bazel command line
- Rule reference
- Use the query command
- Extend Bazel
- Write tests
- Roadmap
- Who is using Bazel?
Reporting a Vulnerability
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.
Contributing to Bazel
See CONTRIBUTING.md
