my rage from v8 is spilling over
Go to file
2020-06-02 19:58:03 +02:00
.github Update mergeable.yml 2020-03-02 15:10:49 -08:00
benchmarks Set execute bit on files if and only if they begin with (#!). (#7347) 2020-04-01 15:28:25 -07:00
cmake Sync from Piper @314226556 2020-06-01 16:32:31 -07:00
conformance Sync from Piper @314226556 2020-06-01 16:32:31 -07:00
csharp initial implementation of buffer encoding 2020-06-02 19:58:03 +02:00
docs Sync from Piper @313142438 2020-05-26 00:26:15 -07:00
editors Sync from Piper @313142438 2020-05-26 00:26:15 -07:00
examples Set execute bit on files if and only if they begin with (#!). (#7347) 2020-04-01 15:28:25 -07:00
java Merge branch '3.12.x' into merge-312 2020-05-26 16:45:43 -07:00
js Sync from Piper @314226556 2020-06-01 16:32:31 -07:00
kokoro Merge branch '3.12.x' into merge-312 2020-05-26 16:45:43 -07:00
m4 Mostly fix Sun Studio configuration using SunCC compiler 2018-09-12 22:18:27 -04:00
objectivec Sync from Piper @313142438 2020-05-26 00:26:15 -07:00
php Simplified PHP testing scripts. (#7574) 2020-05-28 19:24:08 -07:00
protoc-artifacts Update protobuf version (#7557) 2020-05-26 15:46:39 -07:00
python Sync from Piper @314226556 2020-06-01 16:32:31 -07:00
ruby Update protobuf version (#7557) 2020-05-26 15:46:39 -07:00
src Overcome the ref struct limitation for pre-roslyn compilers by introducing GOOGLE_PROTOBUF_REFSTRUCT_COMPATIBILITY_MODE for generated code (#7490) 2020-06-02 00:26:25 -07:00
third_party Update six.BUILD 2019-10-28 16:28:41 -07:00
util/python [bazel] Add fixes for --incompatible_load_{cc,java,proto}_rules_from_bzl (Part 2) 2019-07-29 14:14:04 -07:00
.bazelignore [bazel] Update gtest and deprecate //external:{gtest,gtest_main} (#7237) 2020-03-02 15:15:22 -08:00
.gitignore python: add sphinx docs (#6525) 2020-02-11 11:40:17 -08:00
.gitmodules Include googletest as a submodule (#3993) 2018-03-26 13:54:32 -07:00
.readthedocs.yml python: publish sphinx docs to read the docs 2020-02-28 13:36:50 -06:00
appveyor.bat use netcoreapp2.1 for testing 2019-03-12 05:16:52 -04:00
appveyor.yml Merge branch '3.6.x' into merge-3-6-x 2018-06-25 13:22:10 -07:00
autogen.sh Add cpp tests under release docker image. 2018-07-15 16:41:25 -07:00
BUILD Merge branch '3.12.x' into merge-312 2020-05-26 16:45:43 -07:00
build_files_updated_unittest.sh Copy files to temp-dir for testing 2019-07-24 10:23:55 -07:00
cc_proto_blacklist_test.bzl [bazel] Fix blacklisted_protos in cc_toolchain and add test (#7075) 2020-01-15 10:27:35 -08:00
CHANGES.txt Overcome the ref struct limitation for pre-roslyn compilers by introducing GOOGLE_PROTOBUF_REFSTRUCT_COMPATIBILITY_MODE for generated code (#7490) 2020-06-02 00:26:25 -07:00
compiler_config_setting.bzl [bazel] Move Java runtime/toolchains into //java (#7190) 2020-02-13 13:04:14 -08:00
composer.json Update PHP descriptors (#3391) 2017-08-04 16:35:22 -07:00
configure.ac Update protobuf version (#7557) 2020-05-26 15:46:39 -07:00
CONTRIBUTING.md Update CONTRIBUTING.md 2019-05-31 15:32:02 -07:00
CONTRIBUTORS.txt Add nano proto authors and update LICENSE file to include Android.mk. 2014-11-20 14:27:46 -08: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 Replace repo links. 2018-08-22 11:55:30 -07:00
generate_descriptor_proto.sh Down-integrate from google3. 2018-09-04 10:58:54 -07:00
global.json C# project cleanup 2020-05-27 13:59:51 +02:00
LICENSE Cleanup LICENSE file. 2018-03-26 15:03:41 -07:00
Makefile.am Overcome the ref struct limitation for pre-roslyn compilers by introducing GOOGLE_PROTOBUF_REFSTRUCT_COMPATIBILITY_MODE for generated code (#7490) 2020-06-02 00:26:25 -07:00
post_process_dist.sh Removed javanano from post_process_dist.sh 2018-06-05 09:17:19 -07:00
protobuf_deps.bzl Update rules_cc 2020-05-29 13:05:23 -07:00
Protobuf-C++.podspec Update protobuf version (#7557) 2020-05-26 15:46:39 -07:00
protobuf-lite.pc.in Libs should not include @PTHREAD_CFLAGS@ 2019-02-22 11:19:38 -08:00
protobuf.bzl Fix depset/list confusion in #7458. 2020-05-29 13:05:58 -07:00
protobuf.pc.in Down integrate to GitHub 2019-06-11 16:00:16 -07:00
Protobuf.podspec Update protobuf version (#7557) 2020-05-26 15:46:39 -07:00
README.md Sync from Piper @307316823 2020-04-19 18:01:44 -07:00
tests.sh Simplified PHP testing scripts. (#7574) 2020-05-28 19:24:08 -07:00
update_compatibility_version.py Marked update_compatibility_version.py as executable (#6916) 2019-11-20 16:39:07 -08:00
update_file_lists.sh Add test to verify BUILD- and cmake-files are in sync with src/Makefile.am 2019-07-24 10:23:55 -07:00
update_version.py Update to 3.10.0-rc0 (#6660) 2019-09-18 13:30:03 -07:00
WORKSPACE [bazel] Update gtest and deprecate //external:{gtest,gtest_main} (#7237) 2020-03-02 15:15:22 -08:00

Protocol Buffers - Google's data interchange format

Copyright 2008 Google Inc.

https://developers.google.com/protocol-buffers/

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 release page:

https://github.com/protocolbuffers/protobuf/releases

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 repo here:

https://repo1.maven.org/maven2/com/google/protobuf/protoc/

These pre-built binaries are only provided for released versions. If you want to use the github master 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 Ubuntu MacOS Windows
C++ (include C++ runtime and protoc) src Build status
Build status
Build status
Build status
Build status
Build status
Java java Build status
Build status
Build status
Build status
Python python Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Objective-C objectivec Build status
Build status
Build status
Build status
C# csharp Build status Build status
Build status
JavaScript js Build status Build status
Ruby ruby Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Go golang/protobuf
PHP php Build status
Build status
Build status
Build status
Dart dart-lang/protobuf Build Status

Quick Start

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

https://developers.google.com/protocol-buffers/docs/tutorials

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

Documentation

The complete documentation for Protocol Buffers is available via the web at:

https://developers.google.com/protocol-buffers/