Go to file
Mike Kruskal 035d5ba42d Fix ruby install cache name 2023-01-30 16:10:47 -08:00
.github Fix ruby install cache name 2023-01-30 16:10:47 -08:00
build_defs Breaking change: Migrate to Abseil's logging library. 2023-01-24 21:51:03 -08:00
cmake Add a non-bazel docker action and use it for CMake/PHP tests 2023-01-30 13:40:44 -08:00
conformance Breaking change: Migrate to Abseil's logging library. 2023-01-24 21:51:03 -08:00
csharp Make C# tests more robust against variations due to internal/external builds. 2023-01-27 09:55:16 -08:00
docs Add additional field number allocations for ygot. (#11518) 2023-01-15 14:44:35 -08:00
editors
examples Correct the link name for BUILD.bazel file (#10662) 2022-09-27 12:41:03 -07:00
java Enable new JSON field name conflict handling. 2023-01-18 14:03:23 -08:00
kokoro Remove Abseil patch in tests and bump our Bazel version to 20230125.rc3 2023-01-25 12:04:48 -08:00
objectivec [ObjC] Mark classes that shouldn't be subclassed as such. 2023-01-27 15:21:05 -08:00
php Remove noisy LOG statement in Message Differencer 2023-01-26 10:02:10 -08:00
pkg Add missing test utility to CMake rules. 2023-01-10 19:43:18 -08:00
python Migrating downstream error collectors to use the new string_view overrides. 2023-01-25 10:58:18 -08:00
ruby Mark ruby release alias as manual 2023-01-30 13:40:02 -08:00
src Reorganize secrets/parameterization, fix timeouts 2023-01-30 13:40:00 -08:00
third_party Bump to Abseil 20230125.rc3 for cmake builds (#11663) 2023-01-25 09:41:06 -08:00
toolchain Enable the Copybara sync for all files. 2022-11-01 10:19:37 -07:00
.bazelignore
.bazelrc Squashed 'third_party/utf8_range/' content from commit 72c943dea 2023-01-19 16:02:55 -08:00
.gitignore Implement docker/bazel runner using composite actions 2023-01-30 13:40:44 -08:00
.gitmodules Breaking change: Migrate to Abseil's logging library. 2023-01-24 21:51:03 -08:00
.readthedocs.yml
BUILD.bazel Squashed 'third_party/utf8_range/' content from commit 72c943dea 2023-01-19 16:02:55 -08:00
CHANGES.txt Clean up legacy CHANGES.txt. 2023-01-18 17:39:11 -08:00
CMakeLists.txt Breaking change: Migrate to Abseil's logging library. 2023-01-24 21:51:03 -08:00
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 2022-12-01 09:29:45 -08:00
CONTRIBUTING.md Squashed 'third_party/utf8_range/' content from commit 72c943dea 2023-01-19 16:02:55 -08:00
CONTRIBUTORS.txt
LICENSE Squashed 'third_party/utf8_range/' content from commit 72c943dea 2023-01-19 16:02:55 -08:00
Protobuf-C++.podspec Main 202212161220 (#11340) 2022-12-16 21:47:18 -08:00
Protobuf.podspec Main 202212161220 (#11340) 2022-12-16 21:47:18 -08:00
README.md Squashed 'third_party/utf8_range/' content from commit 72c943dea 2023-01-19 16:02:55 -08:00
SECURITY.md
WORKSPACE Migrate dependencies pointing to github-generated tarballs to use zip instead. 2023-01-30 13:36:57 -08:00
appveyor.bat
appveyor.yml
fix_permissions.sh
generate_changelog.py Sync from Piper @484138213 2022-10-26 20:10:29 -07:00
generate_descriptor_proto.sh
global.json
google3_export_generated_files.sh Bump protobuf to latest upb version. 2023-01-14 00:11:12 -08:00
maven_install.json
protobuf.bzl Add missing mnemonic on a couple of proto compilation actions. 2023-01-17 11:00:10 -08:00
protobuf_deps.bzl Migrate dependencies pointing to github-generated tarballs to use zip instead. 2023-01-30 13:36:57 -08:00
protobuf_release.bzl
protobuf_version.bzl Add ruby release targets (#11468) 2023-01-19 15:11:56 -08:00
push_auto_update.sh Regenerate stale files before every test that requires them. 2022-12-20 18:44:28 -08:00
regenerate_stale_files.sh Add a non-bazel docker action and use it for CMake/PHP tests 2023-01-30 13:40:44 -08:00
update_subtrees.sh Merge branch 'main' into utf8_range_dep 2023-01-19 18:11:34 -08:00
version.json Breaking Change: Switch to releasing ruby source gems only. 2023-01-23 12:56:32 -08:00

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.