commit | edb8085c816c2465361d50f3e378f10123432e9d | [log] [tgz] |
---|---|---|
author | Ulises Mendez Martinez <[email protected]> | Thu Feb 29 10:09:03 2024 +0000 |
committer | Ulises Mendez Martinez <[email protected]> | Thu Feb 29 10:16:29 2024 +0000 |
tree | bad2f7136b11a5dafcb55f54ddd1b10fa1bfd96a | |
parent | d343481b6af548fd10e489ac83f51f517911f7da [diff] |
Add OWNERS, METADATA & LICENSE files. * Setting owners to Kleaf team + default janitors. Bug: 254734455 Change-Id: If8b5d562525efa038e72efe189c7051bdd8852c5 Signed-off-by: Ulises Mendez Martinez <[email protected]>
This repository contains a Starlark implementation of proto_library
and related “base layer” rules in Bazel. It does not provide rules for any specific languages. These are typically expected to be provided in the ruleset for the language.
For a high-level overview of using Protocol Buffers and gRPC with Bazel, see https://bazel-contrib.github.io/SIG-rules-authors/proto-grpc.html.
For the list of Proto rules, see the Bazel documentation.
As of September 2023, this repo is mostly empty and contains stubs for proto_library
, ProtoInfo
and other proto toolchain support rules.
This will change soon, around the time Bazel 7 is released (in Oct/Nov 2023), because the stubs will be replaced with actual implementations. We plan to remove the native implementations in Bazel 8, at which point rules_proto will be the only way to build Protobuf rules.
As such it's recommended to use this repository now, so that the removal of implementations from Bazel 8 does not cause you problems.
To get started with rules_proto
, add the WORKSPACE
file snippet from the latest release.
Then, in your BUILD
files, import and use the rules:
load("@rules_proto//proto:defs.bzl", "proto_library") proto_library( ... )
If you're migrating from the native proto rules to rules_proto
, you can use the following buildifier command to automate the changes to your BUILD
and .bzl
files:
buildifier --lint=fix --warnings=native-proto <path/to/BUILD>
Bazel and rules_proto
are the work of many contributors. We appreciate your help!
To contribute, please read the contribution guidelines: CONTRIBUTING.md.
Note that the rules_proto
use the GitHub issue tracker for bug reports and feature requests only.
For asking questions see:
#proto
on slack.bazel.build