| commit | 3106e3a354de827292250c8325877521b9c69996 | [log] [tgz] |
|---|---|---|
| author | ilist <ilist@google.com> | Wed Nov 03 02:25:58 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 03 02:26:58 2021 -0700 |
| tree | a0b29dd360f1e2afbadd1676889cf4ed28db3b9f | |
| parent | 1eded2f01e5d6ec4c3ae07a942f3034b1587a140 [diff] |
Expose create_proto_info to builtins. This is one of two things proto_library rule does (besides creating descriptor set). It's possible to peel of some layers of create_proto_info to Starlark and this will be done later (now the focus is to get outer layer of proto_library to Starlark). The last layer of create_proto_info is the creation of ProtoInfo provider, which is currently native. It's used a lot by native lang_proto_libraries, thus rewriting it completely to Starlark would create more problems than benefits at the moment. The code can only be used from builtins. ProtoInfo provider needs a lot more thought and consideration, before being made public to Starlark. PiperOrigin-RevId: 407286229
{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
