my rage from v8 is spilling over
Go to file
2016-02-06 08:34:08 -05:00
benchmarks More cleanup, based around searches for "Google.ProtocolBuffers" 2015-06-26 20:13:07 +01:00
cmake Integrate from google internal. 2016-01-29 13:51:05 -08:00
conformance Merge pull request #1145 from jskeet/conformance 2016-01-16 18:28:13 +00:00
csharp Generated code changes from previous commit 2016-02-04 15:02:59 +00:00
editors down-integrate internal changes 2015-05-21 19:32:02 -07:00
examples Merge pull request #1052 from tswast/master 2015-12-17 11:42:59 -08:00
java Restore the license for Internal.java 2016-01-29 14:04:15 -08:00
javanano Update version number and fix javadoc errors. 2016-01-06 15:47:41 -08:00
js Enable JavaScript tests for binary parse/serialize. 2016-02-02 15:54:59 -08:00
m4 Merge pull request #789 from motahan/solaris64_fix 2016-01-20 16:57:01 -08:00
more_tests Add makefile for extended tests to be run before release. 2010-01-12 22:45:15 +00:00
objectivec Integrate from google internal. 2016-01-29 13:51:05 -08:00
protoc-artifacts Fix typos in README.md/CHANGES.txt 2016-01-11 14:52:01 -08:00
python Manually down-integrate python JSON struct support from internal code base. 2016-01-29 18:10:50 -08:00
ruby Fixed Ruby conformance tests by running them under rvm Ruby. 2016-01-11 21:16:42 -08:00
src make 'no syntax' warning useful by showing which file 2016-02-06 08:34:08 -05:00
util/python Added util/python/BUILD to provide //util/python:python_headers dependency for building use_fast_cpp_protos 2015-12-08 09:51:14 -08:00
.gitignore Manually down-integrate python JSON struct support from internal code base. 2016-01-29 18:10:50 -08:00
.travis.yml Added README and enabled JavaScript tests on Node.js 2015-12-21 15:22:49 -08:00
appveyor.bat Improved SHARED build from CMake project 2015-10-15 02:56:48 +03:00
appveyor.yml Down-integrate from internal code base. 2015-12-11 17:10:28 -08:00
autogen.sh Add support for arguments. 2015-10-13 09:42:20 -07:00
BUILD Fix bazel BUILD for Java. 2016-01-21 23:08:33 -08:00
CHANGES.txt Fix typos in README.md/CHANGES.txt 2016-01-11 14:52:01 -08:00
configure.ac Add missing files to EXTRA_DIST. 2015-12-28 14:18:49 -08:00
CONTRIBUTORS.txt Add nano proto authors and update LICENSE file to include Android.mk. 2014-11-20 14:27:46 -08:00
generate_descriptor_proto.sh Integrate from google internal. 2016-01-29 13:51:05 -08:00
gmock.BUILD Fix headers for gmock.BUILD 2015-12-01 22:52:42 +01:00
LICENSE Add support for POWER Linux 2015-11-03 14:49:42 -08:00
Makefile.am Rename Preconditions to ProtoPreconditions 2016-02-04 14:50:43 +00:00
post_process_dist.sh Add js to post_process_dist.sh. 2015-12-28 16:31:10 -08:00
protobuf-lite.pc.in Uncomment conflict fields from pkg-config files. 2015-05-12 17:50:05 +02:00
protobuf.bzl Make protobuf Skylark extension appends the workspace root 2016-01-15 23:12:09 +01:00
protobuf.pc.in Uncomment conflict fields from pkg-config files. 2015-05-12 17:50:05 +02:00
Protobuf.podspec Update podspec version to 3.0.0-beta-2 2016-01-15 20:21:46 -08:00
README.md Refactor README.md. 2016-01-21 17:30:45 -08:00
six.BUILD Add srcs_version = "PY2AND3" in BUILD files 2015-12-03 13:16:06 -08:00
travis.sh Allow conformance test runner to tolerate crashes, and re-enable conformance tests. 2016-01-11 16:15:46 -08:00
update_file_lists.sh Fix bugs on windows 2015-08-25 17:58:48 -07:00
WORKSPACE fix six package path. 2015-10-22 13:44:15 -07:00

Protocol Buffers - Google's data interchange format

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 documentaion 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:

http://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++ Installaton 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 TBD

Usage

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

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