3 releases (breaking)

0.3.0 Nov 2, 2023
0.2.0 Aug 23, 2022
0.1.0 Jul 7, 2022

#1169 in Development tools

Download history 5950/week @ 2024-01-24 6469/week @ 2024-01-31 9018/week @ 2024-02-07 7422/week @ 2024-02-14 7146/week @ 2024-02-21 9269/week @ 2024-02-28 9412/week @ 2024-03-06 7847/week @ 2024-03-13 6097/week @ 2024-03-20 6083/week @ 2024-03-27 8071/week @ 2024-04-03 7438/week @ 2024-04-10 6576/week @ 2024-04-17 6187/week @ 2024-04-24 5546/week @ 2024-05-01 5430/week @ 2024-05-08

24,949 downloads per month
Used in 18 crates

MIT license

143 lines


grpc-build provides an flexible way to manage protobuf files and generate the gRPC code required by tonic.

It is built on top of tonic_build and it extends its functionality by compiling all the protobuf files inside a directory. In addition to that, this library adds another feature: full proto name annotation. This could be useful in cases where you want use the full name (package + message name) to identify a protobuf message. Therefore, for each top-level protobuf message this library adds a method to its generated struct returning its full proto name.

Given the following protobuf definition:

// my_message.proto
package grpc_build;
message Message {}

The library will generate the standard Rust code plus the extra impl for each message.

// Message.rs (generated)
struct Message {}

impl NamedMessage for Message {
    /// This returns package (grpc-build) + message name (Message).
    const NAME: &'static str = "grpc_build.MyMessage"

If the protobuf content is valid (worth linting it), grpc-build will take care of the protobuf imports and it will also generate the mod.rs file to allow the compiler to find the generated code. This file will be placed inside the output directory.

It comes both as a library that can be used directly inside a project and as a binary that can be used in CI pipelines.

Documentation - Crates.io

Getting started

Using it as a binary

Get the latest binary release and use it inside your CI pipeline.

grpc-build build --in-dir="<protobuf directory>" --out-dir="<codegen>"

Depending on the requirements, you can generate the gRPC Client and/or Server by using the --build-client (-c) and --build-server (-s) flags.

To overwrite the contents of the output directory, use the --force (-f) flag.

// both client and server, overwriting the existing protogen
grpc-build build -c -s --in-dir="<protobuf directory>" --out-dir="<codegen>" -f

Using it as a library

The most convenient way of using grpc_build as a library is by taking advantage of Rust's build.rs file. Don't forget to add grpc_build to the build-dependencies list.

// build.rs
use grpc_build::Builder;

fn main() {

If you want to set advanced compilation options (like an additional #[derive] for the generated types), use the build_with_config function, which exposes the underlying tonic_build::Builder.

A more advanced usage is to use the get_protos and refactor functions yourself. The following example does almost the same as the example above, except you don't get the NamedMessage traits auto derived

fn main() {
    let proto_src_dir = "protos";
    let proto_out_dir = "src/protogen";

    let protos: Vec<_> = crate::base::get_protos(proto_src_dir).collect();


        .compile(&protos, &["."])



This project is licensed under the MIT license.


~41K SLoC