Go to file
Matt Kulukundis 10b8034be6 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
PiperOrigin-RevId: 492217200
2022-12-01 09:29:45 -08:00
.github [ObjC] Disable CocoaPods watchOS validation for now. 2022-11-28 08:17:09 -08:00
build_defs Merge tag 'refs/tags/sync-piper' into sync-stage 2022-10-19 16:57:04 -07:00
cmake Update auto-generation script to handle well-known types 2022-11-09 06:57:08 -08:00
conformance Use sys.stdin.buffer and sys.stdout.buffer directly for binary I/O, don't 2022-11-17 15:17:49 -08:00
csharp Expose internal setExtension method for Kotlin 2022-11-29 21:53:03 -08:00
docs Add custom option numbers for use by Buf (#11110) 2022-12-01 09:05:42 -08:00
editors Sync from Piper @acozzette/proto_github_202203101748 2022-03-10 18:36:42 +00:00
examples Sync from Piper @mkruskal/footmitten 2022-09-27 15:18:40 -07:00
java Fix lint warnings for protobuf GeneratedMessage.java 2022-11-30 18:40:11 -08:00
kokoro Internal change 2022-11-30 12:47:03 -08:00
objectivec [ObjC] Move GenerateHeader over to Printer::Emit. 2022-12-01 09:01:42 -08:00
php Bump upb version 2022-11-23 11:09:23 -08:00
pkg Make CMake test_util and lite_test_util mutually exclusive 2022-11-04 14:39:26 -07:00
python Fix copybara transformations for Python/C++ code. 2022-11-30 14:17:12 -08:00
ruby Bump upb version 2022-11-23 11:09:23 -08:00
src [ObjC] Move GenerateHeader over to Printer::Emit. 2022-12-01 09:01:42 -08:00
third_party Fixing merge issues 2022-10-24 14:54:43 -07:00
toolchain Enable the Copybara sync for all files. 2022-11-01 10:19:37 -07:00
.bazelignore Clean up leftover benchmark cruft (#10480) 2022-08-29 16:05:04 -04:00
.bazelrc Fixing merge issues 2022-10-24 14:54:43 -07:00
.gitignore Remove all autotools usage (#10132) 2022-08-10 22:51:29 -07:00
.gitmodules Sync from Piper @480194141 2022-10-10 21:05:53 -07:00
.readthedocs.yml python: publish sphinx docs to read the docs 2020-02-28 13:36:50 -06:00
BUILD.bazel Update auto-generation script to handle well-known types 2022-11-09 06:57:08 -08:00
CHANGES.txt Merge release branch 21.x into main 2022-10-27 12:52:20 +00:00
CMakeLists.txt Copybara import of the project: 2022-11-11 10:34:45 -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 Sync from Piper @441896533 2022-04-14 17:36:14 -07:00
CONTRIBUTORS.txt Sync from Piper @427369078 2022-02-08 20:53:31 -08:00
LICENSE Cleanup LICENSE file. 2018-03-26 15:03:41 -07:00
Protobuf-C++.podspec Merge release branch 21.x into main 2022-10-27 12:52:20 +00:00
Protobuf.podspec Merge release branch 21.x into main 2022-10-27 12:52:20 +00:00
README.md Standardize link formatting in documentation. 2022-11-23 13:54:32 -08:00
SECURITY.md Sync from Piper @391414001 2021-08-17 17:26:34 -07:00
WORKSPACE Upgrade rules_python to newest version. 2022-11-22 15:02:41 -08:00
appveyor.bat Sync from Piper @425656941 2022-02-01 18:24:53 +00:00
appveyor.yml Upgrade to MSVC 2017 (#10437) 2022-08-22 14:29:12 -07:00
fix_permissions.sh Set execute bit on files if and only if they begin with (#!). (#7347) 2020-04-01 15:28:25 -07:00
generate_changelog.py Sync from Piper @484138213 2022-10-26 20:10:29 -07:00
generate_descriptor_proto.sh Sync from Piper @467099277 2022-08-11 20:55:01 -07:00
global.json Sync from Piper @425656941 2022-02-01 18:24:53 +00:00
maven_install.json Adding new kotlin dependency 2022-08-12 13:16:40 -07:00
protobuf.bzl Sync from Piper @480194141 2022-10-10 21:05:53 -07:00
protobuf_deps.bzl Bump upb version 2022-11-23 11:09:23 -08:00
protobuf_release.bzl Sync from Piper @446230931 2022-05-03 17:41:54 +00:00
protobuf_version.bzl cleanups, formatting 2022-10-28 20:55:20 +00:00
push_auto_update.sh Update auto-generation script to handle well-known types 2022-11-09 06:57:08 -08:00
version.json revert version.json from testing 2022-10-28 20:50:55 +00: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.