my rage from v8 is spilling over
Go to file
Daniel Kurka e2461b5f59 Revert "Remove unused f expression from jscode gen. (#5573)"
The removed variable here is actually used breaking downstream bazel
builds.
2019-03-21 14:35:25 -07:00
.github/ISSUE_TEMPLATE Add github issue templates 2018-06-19 11:52:03 -07:00
benchmarks fix macos build for High Sierra (#5780) 2019-02-26 15:51:04 -08:00
cmake Added io_win32.h to header list in CMake config 2019-03-21 10:30:37 -07:00
conformance Replace strptime with custom implementation (#5906) 2019-03-19 22:27:13 -07:00
csharp Parse nested listvalue in json for ruby (#5867) 2019-03-12 10:56:58 -07:00
docs Add proto3 to solidity link 2019-01-16 19:47:12 -08:00
editors Improve fix for https://github.com/google/protobuf/issues/295 2017-05-23 15:27:29 +02:00
examples Updated Bazel workspace in examples/ to handle zlib dependency 2018-12-11 16:52:50 -08:00
java Update version number to 3.7.0 (#5793) 2019-02-28 12:55:14 -08:00
js Update version number to 3.7.0 (#5793) 2019-02-28 12:55:14 -08:00
kokoro Update version number to 3.7.0 (#5793) 2019-02-28 12:55:14 -08:00
m4 Mostly fix Sun Studio configuration using SunCC compiler 2018-09-12 22:18:27 -04:00
objectivec ObjC: Add a Xcode project for tvOS. 2019-01-08 08:22:12 -05:00
php Replace strptime with custom implementation (#5906) 2019-03-19 22:27:13 -07:00
protoc-artifacts Update version number to 3.7.0 (#5793) 2019-02-28 12:55:14 -08:00
python Update version number to 3.7.0 (#5793) 2019-02-28 12:55:14 -08:00
ruby Replace strptime with custom implementation (#5906) 2019-03-19 22:27:13 -07:00
src Revert "Remove unused f expression from jscode gen. (#5573)" 2019-03-21 14:35:25 -07:00
third_party Add Bazel config for zlib support (#5389) 2018-12-11 11:58:26 -08:00
util/python Remove hack for building Python support with Bazel. 2016-02-25 12:52:21 -08:00
.gitignore Php 7.3 fix (#5434) 2018-12-18 10:57:03 -08:00
.gitmodules Include googletest as a submodule (#3993) 2018-03-26 13:54:32 -07:00
appveyor.bat Appveyor MinGW build 2018-05-03 03:17:19 +03: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 Bazel: Add dependency to error_prone_annotations 2019-03-08 12:54:49 -08:00
CHANGES.txt Update CHANGES.txt 2019-01-24 14:35:47 -08:00
compiler_config_setting.bzl Create compiler_config_setting.bzl 2018-08-28 14:10:46 +02:00
composer.json Update PHP descriptors (#3391) 2017-08-04 16:35:22 -07:00
configure.ac Update version number to 3.7.0 (#5793) 2019-02-28 12:55:14 -08:00
CONTRIBUTING.md Add constributing guidelines. 2018-08-29 15:50:16 -07:00
CONTRIBUTORS.txt Add nano proto authors and update LICENSE file to include Android.mk. 2014-11-20 14:27:46 -08: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
LICENSE Cleanup LICENSE file. 2018-03-26 15:03:41 -07:00
Makefile.am add type errors test to Makefile.am 2019-03-14 11:37:39 -07:00
post_process_dist.sh Removed javanano from post_process_dist.sh 2018-06-05 09:17:19 -07:00
protobuf-lite.pc.in Uncomment conflict fields from pkg-config files. 2015-05-12 17:50:05 +02:00
protobuf.bzl Down-integrate internal changes (#5467) 2018-12-14 16:05:03 -08:00
protobuf.pc.in Uncomment conflict fields from pkg-config files. 2015-05-12 17:50:05 +02:00
Protobuf.podspec Update version number to 3.7.0 (#5793) 2019-02-28 12:55:14 -08:00
README.md Update kokoro badges for python tests (#5495) 2018-12-19 16:08:57 -08:00
six.BUILD Add srcs_version = "PY2AND3" in BUILD files 2015-12-03 13:16:06 -08:00
tests.sh Add terminating character to zend_lookup_class call (#5871) (#5885) 2019-03-13 13:31:55 -07:00
update_file_lists.sh fix duplicate mkdir in update_file_lists.sh 2018-04-25 08:22:30 +02:00
update_version.py Date and time need to be before version (#5777) 2019-02-25 15:13:59 -08:00
WORKSPACE Bazel: Add dependency to error_prone_annotations 2019-03-08 12:54:49 -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
Java java 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
Build status
Objective-C objectivec Build status
Build status
Build status
Build status
C# csharp Build status Build status
JavaScript js Build status Build status
Ruby ruby 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/