Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Mike Kruskal 037f06d96d Remove mergeable action to allow copybara test reuse. 2 years ago
.github Remove mergeable action to allow copybara test reuse. 2 years ago
build_defs Breaking change: Migrate to Abseil's logging library. 2 years ago
cmake Breaking change: Migrate to Abseil's logging library. 2 years ago
conformance Breaking change: Migrate to Abseil's logging library. 2 years ago
csharp Auto-generate files after cl/506075942 2 years ago
docs Add additional field number allocations for ygot. (#11518) 2 years ago
editors Sync from Piper @acozzette/proto_github_202203101748 3 years ago
examples Correct the link name for BUILD.bazel file (#10662) 2 years ago
java Enable new JSON field name conflict handling. 2 years ago
kokoro Delete Kokoro Linux C++ tests in favor of GHA. 2 years ago
objectivec [ObjC] Error when appearing to use newer generated code. 2 years ago
php Update protobuf's UPB dep to include the most recent changes. 2 years ago
pkg Add missing test utility to CMake rules. 2 years ago
python Migrating downstream error collectors to use the new string_view overrides. 2 years ago
ruby Migrate Bazel C++ Linux tests to Github Actions (#11702) 2 years ago
src Auto-generate files after cl/506345156 2 years ago
third_party Bump to Abseil 20230125.rc3 for cmake builds (#11663) 2 years ago
toolchain Enable the Copybara sync for all files. 2 years ago
.bazelignore Clean up leftover benchmark cruft (#10480) 2 years ago
.bazelrc Add sanitized builds to Kokoro (#10706) 2 years ago
.gitignore Bazelify ruby runtime (#10525) 2 years ago
.gitmodules Breaking change: Migrate to Abseil's logging library. 2 years ago
.readthedocs.yml python: publish sphinx docs to read the docs 5 years ago
BUILD.bazel Bazelify ruby runtime (#10525) 2 years ago
CHANGES.txt Clean up legacy CHANGES.txt. 2 years ago
CMakeLists.txt Breaking change: Migrate to Abseil's logging library. 2 years ago
CODE_OF_CONDUCT.md Add a code of conduct based on https://www.contributor-covenant.org/ and https://github.com/carbon-language/carbon-lang/blob/trunk/CODE_OF_CONDUCT.md 2 years ago
CONTRIBUTING.md Sync from Piper @441896533 3 years ago
CONTRIBUTORS.txt Sync from Piper @427369078 3 years ago
LICENSE Cleanup LICENSE file. 7 years ago
Protobuf-C++.podspec Main 202212161220 (#11340) 2 years ago
Protobuf.podspec Main 202212161220 (#11340) 2 years ago
README.md Standardize link formatting in documentation. 2 years ago
SECURITY.md Sync from Piper @391414001 3 years ago
WORKSPACE Migrate dependencies pointing to github-generated tarballs to use zip instead. 2 years ago
appveyor.bat Sync from Piper @425656941 3 years ago
appveyor.yml Upgrade to MSVC 2017 (#10437) 2 years ago
fix_permissions.sh Set execute bit on files if and only if they begin with (#!). (#7347) 5 years ago
generate_changelog.py Sync from Piper @484138213 2 years ago
generate_descriptor_proto.sh Sync from Piper @467099277 2 years ago
global.json Sync from Piper @425656941 3 years ago
google3_export_generated_files.sh Bump protobuf to latest upb version. 2 years ago
maven_install.json Adding new kotlin dependency 2 years ago
protobuf.bzl Add missing mnemonic on a couple of proto compilation actions. 2 years ago
protobuf_deps.bzl Update protobuf's UPB dep to include the most recent changes. 2 years ago
protobuf_release.bzl Sync from Piper @446230931 3 years ago
protobuf_version.bzl Add ruby release targets (#11468) 2 years ago
push_auto_update.sh Regenerate stale files before every test that requires them. 2 years ago
regenerate_stale_files.sh Breaking change: Migrate to Abseil's logging library. 2 years ago
update_subtrees.sh Merge branch 'main' into utf8_range_dep 2 years ago
version.json Undo ruby major version bump based on discussions with cloud team. 2 years ago

README.md

Protocol Buffers - Google's data interchange format

Copyright 2008 Google Inc.

Protocol Buffers documentation

Overview

Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. You can find protobuf's documentation on the Google Developers site.

This README file contains protobuf installation instructions. To install protobuf, you need to install the protocol compiler (used to compile .proto files) and the protobuf runtime for your chosen programming language.

Protocol Compiler Installation

The protocol compiler is written in C++. If you are using C++, please follow the C++ Installation Instructions to install protoc along with the C++ runtime.

For non-C++ users, the simplest way to install the protocol compiler is to download a pre-built binary from our GitHub release page.

In the downloads section of each release, you can find pre-built binaries in zip packages: protoc-$VERSION-$PLATFORM.zip. It contains the protoc binary as well as a set of standard .proto files distributed along with protobuf.

If you are looking for an old version that is not available in the release page, check out the Maven repository.

These pre-built binaries are only provided for released versions. If you want to use the github main version at HEAD, or you need to modify protobuf code, or you are using C++, it's recommended to build your own protoc binary from source.

If you would like to build protoc binary from source, see the C++ Installation Instructions.

Protobuf Runtime Installation

Protobuf supports several different programming languages. For each programming language, you can find instructions in the corresponding source directory about how to install protobuf runtime for that specific language:

Language Source
C++ (include C++ runtime and protoc) src
Java java
Python python
Objective-C objectivec
C# csharp
Ruby ruby
Go protocolbuffers/protobuf-go
PHP php
Dart dart-lang/protobuf
Javascript protocolbuffers/protobuf-javascript

Quick Start

The best way to learn how to use protobuf is to follow the tutorials in our developer guide.

If you want to learn from code examples, take a look at the examples in the examples directory.

Documentation

The complete documentation is available via the Protocol Buffers documentation.

Developer Community

To be alerted to upcoming changes in Protocol Buffers and connect with protobuf developers and users, join the Google Group.