my rage from v8 is spilling over
Go to file
2018-08-30 11:45:39 -04:00
.github/ISSUE_TEMPLATE Add github issue templates 2018-06-19 11:52:03 -07:00
benchmarks Replace repo links. 2018-08-22 11:55:30 -07:00
cmake Replace repo links. 2018-08-22 11:55:30 -07:00
conformance Replace repo links. 2018-08-22 11:55:30 -07:00
csharp Replace repo links. 2018-08-22 11:55:30 -07:00
docs Replace repo links. 2018-08-22 11:55:30 -07:00
editors Improve fix for https://github.com/google/protobuf/issues/295 2017-05-23 15:27:29 +02:00
examples Replace repo links. 2018-08-22 11:55:30 -07:00
java Replace repo links. 2018-08-22 11:55:30 -07:00
js Replace repo links. 2018-08-22 11:55:30 -07:00
kokoro Revert changed links in Dockerfiles. 2018-08-23 12:43:35 -07:00
m4 Merge pull request #1333 from cgull/pkg-config-issue 2018-03-12 14:13:13 -07:00
objectivec Replace repo links. 2018-08-22 11:55:30 -07:00
php Replace repo links. 2018-08-22 11:55:30 -07:00
protoc-artifacts Replace repo links. 2018-08-22 11:55:30 -07:00
python Replace repo links. 2018-08-22 11:55:30 -07:00
ruby Replace repo links. 2018-08-22 11:55:30 -07:00
src Also make sure known fields come across as expected 2018-08-30 11:45:39 -04:00
third_party Include googletest as a submodule (#3993) 2018-03-26 13:54:32 -07:00
util/python Remove hack for building Python support with Bazel. 2016-02-25 12:52:21 -08:00
.gitignore Ignore python .egg file to make git status clean #5004 2018-08-05 02:58:30 -07: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 21:03:55 -07:00
BUILD Update build files. 2018-08-13 14:41:27 -07:00
CHANGES.txt Replace repo links. 2018-08-22 11:55:30 -07:00
composer.json Update PHP descriptors (#3391) 2017-08-04 16:35:22 -07:00
configure.ac Merge branch '3.6.x' into merge-3-6-x 2018-08-01 13:44:55 -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 Merge from Google internal for 3.4 release 2017-07-18 15:38:30 -07:00
LICENSE Cleanup LICENSE file. 2018-03-26 15:03:41 -07:00
Makefile.am Fix failing tests. 2018-08-09 21:21:01 -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 Change deprecated Bazel single file attr param 2018-08-14 21:55:35 -06:00
protobuf.pc.in Uncomment conflict fields from pkg-config files. 2015-05-12 17:50:05 +02:00
Protobuf.podspec Replace repo links. 2018-08-22 11:55:30 -07:00
README.md Replace repo links. 2018-08-22 11:55:30 -07:00
six.BUILD Add srcs_version = "PY2AND3" in BUILD files 2015-12-03 13:16:06 -08:00
tests.sh Fix go tests. 2018-08-23 15:35:52 -07:00
update_file_lists.sh fix duplicate mkdir in update_file_lists.sh 2018-04-25 08:22:30 +02:00
WORKSPACE Merge pull request #4168 from jin/master 2018-06-22 17:47:17 -07: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
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
Go golang/protobuf
PHP php Build status
Build status
Build status
Build status
Dart dart-lang/protobuf

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/