my rage from v8 is spilling over
Go to file
2016-07-13 15:37:29 -07:00
benchmarks Add the missing maintiner-clean entry for benchmarks 2016-05-06 12:47:41 -04:00
cmake Integrate from internal code base. 2016-07-13 13:48:40 -07:00
conformance Fix spelling in strings and comments 2016-07-03 15:26:04 +03:00
csharp Update generated files. 2016-07-13 15:37:29 -07:00
docs Add https://github.com/os72/protobuf-dynamic 2016-05-31 22:07:14 -07:00
editors down-integrate internal changes 2015-05-21 19:32:02 -07:00
examples Integrate from internal code base. 2016-07-13 13:48:40 -07:00
java Integrate from internal code base. 2016-07-13 13:48:40 -07:00
javanano Fix spelling in strings and comments 2016-07-03 15:26:04 +03:00
jenkins Rearranged and commented files for running under Jenkins. 2016-03-04 14:34:30 -08:00
js Integrate from internal code base. 2016-07-13 13:48:40 -07: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 Drop the performace baselines. 2016-07-08 12:21:53 -04:00
php Fix spelling in strings and comments 2016-07-03 15:26:04 +03:00
protoc-artifacts Merge pull request #1559 from google/beta-3 2016-05-18 11:44:56 -07:00
python Integrate from internal code base. 2016-07-13 13:48:40 -07:00
ruby Fix spelling in strings and comments 2016-07-03 15:26:04 +03:00
src Update generated files. 2016-07-13 15:37:29 -07:00
util/python Remove hack for building Python support with Bazel. 2016-02-25 12:52:21 -08:00
.gitignore Expand the OS X/Xcode gitignores 2016-05-19 10:08:51 -04:00
.travis.yml Add the CocoaPods integration tests to Travis. 2016-06-14 14:26:01 -04: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 Bazel build: Keep generated sources and Python runtime in the same directory. 2016-05-25 18:02:09 -07:00
CHANGES.txt Update changes for lite 2016-05-16 11:20:33 -07:00
configure.ac Update the list of places where the version is stored. 2016-05-28 01:04:26 -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_descriptor_proto.sh Merge branch 'master' of github.com:google/protobuf 2016-03-30 11:43:44 -07: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 Remove the baseline files from the make dist file list. 2016-07-12 11:35:28 -04: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 Bazel build: Keep generated sources and Python runtime in the same directory. 2016-05-25 18:02:09 -07:00
protobuf.pc.in Uncomment conflict fields from pkg-config files. 2015-05-12 17:50:05 +02:00
Protobuf.podspec Don't #import the .m files. 2016-07-07 08:45:18 -04:00
README.md Fix typos in README.md 2016-01-25 21:41:31 +01:00
six.BUILD Add srcs_version = "PY2AND3" in BUILD files 2015-12-03 13:16:06 -08:00
tests.sh Add the CocoaPods integration tests to Travis. 2016-06-14 14:26:01 -04:00
update_file_lists.sh Fix bugs on windows 2015-08-25 17:58:48 -07:00
WORKSPACE add java/util support based on java/util/pom.xml 2016-03-11 18:08:09 -08: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 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:

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++ 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 TBD

Usage

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

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