How to Generate Code from Proto Files for Different Languages

One of the powerful features of Protocol Buffers (protobuf) is the ability to generate code for multiple programming languages from a single .proto file. This article will provide a detailed guide on how to use the protobuf compiler to generate code files for different languages.

Installing the Protocol Buffers Compiler

Method 1: Official Pre-compiled Binaries

Visit Protocol Buffers GitHub Releases
Download the pre-compiled version for your operating system
Extract and add the protoc executable to your system PATH

Method 2: Package Manager Installation

macOS (using Homebrew):

brew install protobuf

Ubuntu/Debian:

sudo apt-get install protobuf-compiler

Windows (using Chocolatey):

choco install protoc

Verify Installation

protoc --version

Basic Syntax and Commands

Basic Command Format

protoc [OPTION] PROTO_FILES

Common Options

--proto_path=PATH or -I PATH: Specify search path for .proto files
--LANG_out=DST_DIR: Specify output directory and language for generated code
--descriptor_set_out=FILE: Generate descriptor set file

Supported Programming Languages

protobuf officially supports code generation for the following languages:

C++: --cpp_out
Java: --java_out
Python: --python_out
Go: --go_out
Ruby: --ruby_out
Objective-C: --objc_out
C#: --csharp_out
JavaScript: --js_out
PHP: --php_out
Dart: --dart_out

Practical Examples

Let's assume we have the following user.proto file:

syntax = "proto3";

package example;

option go_package = "./pb";
option java_package = "com.example.proto";
option java_outer_classname = "UserProto";

message User {
  int32 id = 1;
  string name = 2;
  string email = 3;
  repeated string tags = 4;
}

service UserService {
  rpc GetUser(GetUserRequest) returns (User);
  rpc CreateUser(CreateUserRequest) returns (User);
}

message GetUserRequest {
  int32 id = 1;
}

message CreateUserRequest {
  string name = 1;
  string email = 2;
  repeated string tags = 3;
}

Generating Code for Different Languages

1. Generate Go Code

# Basic generation
protoc --go_out=. user.proto

# Generate gRPC service code
protoc --go_out=. --go-grpc_out=. user.proto

# Specify output directory
protoc --go_out=./generated --go-grpc_out=./generated user.proto

Generated files:

user.pb.go: Message type definitions
user_grpc.pb.go: gRPC service definitions

2. Generate Java Code

# Generate Java classes
protoc --java_out=./src/main/java user.proto

# Generate gRPC service code (requires gRPC Java plugin)
protoc --java_out=./src/main/java --grpc-java_out=./src/main/java user.proto

3. Generate Python Code

# Generate Python modules
protoc --python_out=. user.proto

# Generate gRPC service code
protoc --python_out=. --grpc_python_out=. user.proto

Generated files:

user_pb2.py: Message type definitions
user_pb2_grpc.py: gRPC service definitions

4. Generate JavaScript Code

# Generate CommonJS modules
protoc --js_out=import_style=commonjs,binary:. user.proto

# Generate ES6 modules
protoc --js_out=import_style=es6,binary:. user.proto

# Generate TypeScript definitions
protoc --js_out=import_style=commonjs,binary:. --ts_out=. user.proto

5. Generate C++ Code

# Generate C++ header and source files
protoc --cpp_out=. user.proto

Generated files:

user.pb.h: Header file
user.pb.cc: Source file

Advanced Usage

1. Multiple File Generation

# Generate multiple proto files at once
protoc --go_out=. *.proto

# Specify multiple files
protoc --go_out=. user.proto order.proto product.proto

2. Specify Import Paths

# Specify proto file search paths
protoc -I./protos -I./common --go_out=. user.proto

3. Generate Descriptor Files

# Generate binary descriptor file
protoc --descriptor_set_out=user.desc user.proto

# Include imported files
protoc --descriptor_set_out=user.desc --include_imports user.proto

4. Custom Options

# Go language specific options
protoc --go_out=. --go_opt=paths=source_relative user.proto

# Java language specific options
protoc --java_out=. --java_opt=annotate_code user.proto

Automation with Makefile

Create a Makefile to automate the code generation process:

.PHONY: gen-go gen-java gen-python gen-all clean

# Define variables
PROTO_DIR := ./protos
GO_OUT_DIR := ./generated/go
JAVA_OUT_DIR := ./generated/java
PYTHON_OUT_DIR := ./generated/python

# Generate Go code
gen-go:
	mkdir -p $(GO_OUT_DIR)
	protoc -I$(PROTO_DIR) --go_out=$(GO_OUT_DIR) --go-grpc_out=$(GO_OUT_DIR) $(PROTO_DIR)/*.proto

# Generate Java code
gen-java:
	mkdir -p $(JAVA_OUT_DIR)
	protoc -I$(PROTO_DIR) --java_out=$(JAVA_OUT_DIR) $(PROTO_DIR)/*.proto

# Generate Python code
gen-python:
	mkdir -p $(PYTHON_OUT_DIR)
	protoc -I$(PROTO_DIR) --python_out=$(PYTHON_OUT_DIR) --grpc_python_out=$(PYTHON_OUT_DIR) $(PROTO_DIR)/*.proto

# Generate all languages
gen-all: gen-go gen-java gen-python

# Clean generated files
clean:
	rm -rf ./generated

Usage:

# Generate Go code
make gen-go

# Generate all language code
make gen-all

# Clean generated files
make clean

Script Automation

Bash Script Example

#!/bin/bash

# generate.sh
set -e

PROTO_DIR="./protos"
OUT_DIR="./generated"

# Create output directories
mkdir -p "$OUT_DIR/go"
mkdir -p "$OUT_DIR/java"
mkdir -p "$OUT_DIR/python"
mkdir -p "$OUT_DIR/js"

echo "Generating Go code..."
protoc -I"$PROTO_DIR" --go_out="$OUT_DIR/go" --go-grpc_out="$OUT_DIR/go" "$PROTO_DIR"/*.proto

echo "Generating Java code..."
protoc -I"$PROTO_DIR" --java_out="$OUT_DIR/java" "$PROTO_DIR"/*.proto

echo "Generating Python code..."
protoc -I"$PROTO_DIR" --python_out="$OUT_DIR/python" --grpc_python_out="$OUT_DIR/python" "$PROTO_DIR"/*.proto

echo "Generating JavaScript code..."
protoc -I"$PROTO_DIR" --js_out=import_style=commonjs,binary:"$OUT_DIR/js" "$PROTO_DIR"/*.proto

echo "Code generation completed!"

PowerShell Script Example

# generate.ps1
$ProtoDir = "./protos"
$OutDir = "./generated"

# Create output directories
New-Item -ItemType Directory -Force -Path "$OutDir/go"
New-Item -ItemType Directory -Force -Path "$OutDir/java"
New-Item -ItemType Directory -Force -Path "$OutDir/python"
New-Item -ItemType Directory -Force -Path "$OutDir/js"

Write-Host "Generating Go code..."
protoc -I"$ProtoDir" --go_out="$OutDir/go" --go-grpc_out="$OutDir/go" "$ProtoDir/*.proto"

Write-Host "Generating Java code..."
protoc -I"$ProtoDir" --java_out="$OutDir/java" "$ProtoDir/*.proto"

Write-Host "Generating Python code..."
protoc -I"$ProtoDir" --python_out="$OutDir/python" --grpc_python_out="$OutDir/python" "$ProtoDir/*.proto"

Write-Host "Generating JavaScript code..."
protoc -I"$ProtoDir" --js_out="import_style=commonjs,binary:$OutDir/js" "$ProtoDir/*.proto"

Write-Host "Code generation completed!"

Common Issues and Solutions

1. protoc Command Not Found

Issue: protoc: command not found

Solution:

Ensure protoc is properly installed
Check that PATH environment variable includes protoc installation path
On Windows, you may need to restart command line or IDE

2. Cannot Find Imported Proto Files

Issue: Import "common/types.proto" was not found

Solution:

# Use -I option to specify search paths
protoc -I. -I./common --go_out=. user.proto

3. Incorrect Package Names in Generated Code

Issue: Go package name or Java package name doesn't match expectations

Solution: Add appropriate options in .proto file:

option go_package = "github.com/yourorg/yourproject/pb";
option java_package = "com.yourorg.yourproject.proto";

4. gRPC Plugin Not Found

Issue: protoc-gen-go-grpc: program not found or is not executable

Solution:

# Install gRPC Go plugin
go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@latest

# Ensure $GOPATH/bin is in PATH
export PATH="$PATH:$(go env GOPATH)/bin"

Best Practices

1. Project Structure Organization

project/
├── protos/           # Store .proto files
│   ├── common/
│   ├── user/
│   └── order/
├── generated/        # Generated code
│   ├── go/
│   ├── java/
│   ├── python/
│   └── js/
├── scripts/          # Generation scripts
│   ├── generate.sh
│   └── generate.ps1
└── Makefile

2. Version Control

Include .proto files in version control
Consider whether to include generated code in version control (usually not recommended)
Exclude generated code directories in .gitignore

3. CI/CD Integration

Automate code generation in CI/CD pipelines:

# GitHub Actions example
name: Generate Proto Code

on:
  push:
    paths:
      - 'protos/**'

jobs:
  generate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      
      - name: Install protoc
        run: |
          sudo apt-get update
          sudo apt-get install -y protobuf-compiler
          
      - name: Generate code
        run: |
          chmod +x ./scripts/generate.sh
          ./scripts/generate.sh
          
      - name: Commit generated code
        run: |
          git config --local user.email "[email protected]"
          git config --local user.name "GitHub Action"
          git add generated/
          git commit -m "Auto-generate proto code" || exit 0
          git push

Conclusion

With the Protocol Buffers compiler, we can easily generate code for multiple programming languages from a single .proto file. Key takeaways include:

Proper installation and configuration of the protoc compiler
Understanding command-line options and language-specific parameters
Organizing project structure and automation scripts
Handling common issues like paths and package name configurations
Integration into development workflow for automated code generation

Mastering these skills will enable you to efficiently use Protocol Buffers in multi-language projects, achieving unified data structure definitions and cross-language communication.

How to Generate Code from Proto Files for Different Languages

Installing the Protocol Buffers Compiler

Method 1: Official Pre-compiled Binaries

Method 2: Package Manager Installation

Verify Installation

Basic Syntax and Commands

Basic Command Format

Common Options

Supported Programming Languages

Practical Examples

Generating Code for Different Languages

1. Generate Go Code

2. Generate Java Code

3. Generate Python Code

4. Generate JavaScript Code

5. Generate C++ Code

Advanced Usage

1. Multiple File Generation

2. Specify Import Paths

3. Generate Descriptor Files

4. Custom Options

Automation with Makefile

Script Automation

Bash Script Example

PowerShell Script Example

Common Issues and Solutions

1. protoc Command Not Found

2. Cannot Find Imported Proto Files

3. Incorrect Package Names in Generated Code

4. gRPC Plugin Not Found

Best Practices

1. Project Structure Organization

2. Version Control

3. CI/CD Integration

Conclusion

Related Posts