commit | 673e59ea247296c95c51ac01de67f4de8f7a846a | [log] [tgz] |
---|---|---|
author | A Googler <no-reply@google.com> | Wed Sep 20 08:39:36 2023 -0700 |
committer | Blaze Rules Copybara <blaze-rules@google.com> | Wed Sep 20 08:40:10 2023 -0700 |
tree | 678311e10c345c52fdd30c32cdea5f4d9ef30da1 | |
parent | bb745f946a0b033dc50b7671bea10c9395e53e4d [diff] |
Wrap proto_lang_toolchain into a macro creating a toolchain Issue: https://github.com/bazelbuild/rules_proto/issues/179 PiperOrigin-RevId: 566975629
This repository contains Starlark implementation of Protobuf rules in Bazel.
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.
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