my rage from v8 is spilling over
Go to file
2017-10-18 16:28:12 -07:00
benchmarks Added C++ benchmark. (#1525) 2016-09-23 11:07:45 -07:00
cmake Merge from google internal 2017-10-18 12:22:18 -07:00
conformance Fix JS conformance tests 2017-10-18 15:09:21 -07:00
csharp Update descriptor protos 2017-10-18 14:21:22 -07:00
docs Add Elixir protobuf and gRPC to 3rd party doc 2017-08-23 00:03:01 +08:00
editors Improve fix for https://github.com/google/protobuf/issues/295 2017-05-23 15:27:29 +02:00
examples Fix go example test. 2017-09-13 17:04:13 -07:00
java Merge from google internal 2017-10-18 12:22:18 -07:00
javanano Add a notice for nano. 2017-03-16 16:09:41 -07:00
jenkins Add Python 3.5 3.6 2017-08-22 15:59:27 -07:00
js Merge from google internal 2017-10-18 12:22:18 -07:00
kokoro Remove pre-installed softwares 2017-08-23 12:35:09 -07:00
m4 Add std::forward and std::move autoconf check 2017-08-15 11:44:16 -07:00
more_tests Add makefile for extended tests to be run before release. 2010-01-12 22:45:15 +00:00
objectivec Update descriptor protos 2017-10-18 14:21:22 -07:00
php Update descriptor protos 2017-10-18 14:21:22 -07:00
protoc-artifacts Merge remote-tracking branch 'origin/3.4.x' into master 2017-10-11 14:44:03 -07:00
python Merge from google internal 2017-10-18 12:22:18 -07:00
ruby Merge remote-tracking branch 'origin/3.4.x' into master 2017-10-11 14:44:03 -07:00
src Fix Java 1.6 compile 2017-10-18 16:28:12 -07:00
third_party Added C++ benchmark. (#1525) 2016-09-23 11:07:45 -07:00
util/python Remove hack for building Python support with Bazel. 2016-02-25 12:52:21 -08:00
.gitignore Fix ruby segment fault (#3708) 2017-10-03 17:28:49 -07:00
.gitmodules Added C++ benchmark. (#1525) 2016-09-23 11:07:45 -07:00
.travis.yml Move travis to the Xcode 8.3 (8.3.3) image. 2017-08-07 12:57:59 -04:00
appveyor.bat Convert C# projects to MSBuild (csproj) format 2017-05-24 09:07:33 +01:00
appveyor.yml Convert C# projects to MSBuild (csproj) format 2017-05-24 09:07:33 +01:00
autogen.sh Update autogen.sh 2017-09-04 15:43:54 +08:00
BUILD Fix bazel build 2017-10-18 14:31:23 -07:00
CHANGES.txt Update CHANGES.txt 2017-08-16 14:40:59 -07:00
composer.json Update PHP descriptors (#3391) 2017-08-04 16:35:22 -07:00
configure.ac Bump version for minor release 2017-09-14 11:12: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 generate_changelog.py: flush output so piping works correctly. 2016-12-09 16:13:18 -08:00
generate_descriptor_proto.sh Merge from Google internal for 3.4 release 2017-07-18 15:38:30 -07:00
gmock.BUILD Update repo to use google test 2016-09-09 13:10:56 -04:00
LICENSE Add support for POWER Linux 2015-11-03 14:49:42 -08:00
Makefile.am Fix distcheck 2017-10-11 15:10:54 -07:00
post_process_dist.sh Add php files for make dist. 2016-10-10 11:44:21 -07:00
protobuf-lite.pc.in Uncomment conflict fields from pkg-config files. 2015-05-12 17:50:05 +02:00
protobuf.bzl Make .bzl files compatible with future versions of Bazel 2017-08-07 20:04:00 +02:00
protobuf.pc.in Uncomment conflict fields from pkg-config files. 2015-05-12 17:50:05 +02:00
Protobuf.podspec Bump version for minor release 2017-09-14 11:12:55 -07:00
README.md Add bazel support for examples. 2017-09-08 16:01:49 -07:00
six.BUILD Add srcs_version = "PY2AND3" in BUILD files 2015-12-03 13:16:06 -08:00
tests.sh Merge remote-tracking branch 'origin/3.4.x' into master 2017-10-11 14:44:03 -07:00
update_file_lists.sh Fix C++ build for down-integration. 2017-03-29 14:52:33 -07:00
WORKSPACE bazel: Add proto_library rules for well known types. Fixes #2763 2017-09-05 22:33:54 +02:00

Protocol Buffers - Google's data interchange format

Build Status Build status Build Status Build Status Build Status

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/google/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
C++ (include C++ runtime and protoc) src
Java java
Python python
Objective-C objectivec
C# csharp
JavaNano javanano
JavaScript js
Ruby ruby
Go golang/protobuf
PHP php
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/