API to generate .rs files for ttrpc from protobuf

API to generate .rs files to be used e. g. from build.rs.

Example

build.rs:

use ttrpc_codegen::Codegen;
use ttrpc_codegen::{Customize, ProtobufCustomize};

fn main() {
    let protos = vec![
        "protos/a.proto",
        "protos/b.proto",
    ];

    Codegen::new()
        .out_dir("protocols/sync")
        .inputs(&protos)
        .include("protocols/protos")
        .rust_protobuf()
        .customize(Customize {
            ..Default::default()
        })
        .rust_protobuf_customize(ProtobufCustomize::default())
        .run()
        .expect("Gen code failed.");
}

Well-known types

Canonical Google well-known type imports such as google/protobuf/timestamp.proto and google/protobuf/empty.proto are resolved automatically. They do not need to be copied into the source tree or added through an extra include directory.

When an imported well-known type is used as an RPC input or output, generated services reference the type provided by the protobuf runtime. A well-known proto explicitly listed as an input keeps using its locally generated module for compatibility. Proto definitions outside the standard well-known type set, including Google API definitions, must still be available through an include directory.

Cargo.toml:

[build-dependencies]
ttrpc-codegen = "0.7.0"

Versions

Use these release pairs:

Version 0.7 requires Rust 1.80 or newer and uses ttrpc-compiler 0.9. Import Customize from ttrpc_codegen to use the matching compiler type. Regenerate bindings and review the runtime changelog when upgrading from 0.6; see the changelog for API details.

Alternative

For manual rust-protobuf service generation with protoc, use the ttrpc-compiler plugin. For Prost messages and services, use the separate ttrpc-codegen-prost package.