my rage from v8 is spilling over
Go to file
Jan Tattermusch 94cbf009e9
Merge pull request #6499 from ObsidianMinor/csharp/proto2-feature/docs
Document proto2 feature implementations in Google.Protobuf
2019-09-03 12:15:52 +02:00
.github Updated issue templates to remove question form (#6576) 2019-08-30 10:58:11 -07:00
benchmarks Add missing files under benchmarks/ to the dist (#6580) 2019-08-27 13:16:28 -07:00
cmake Address review comments 2019-07-24 10:23:55 -07:00
conformance Sync upb (#6577) 2019-08-27 13:14:57 -07:00
csharp Use proto2 and proto3 in unknown field tests 2019-08-29 18:07:02 -05:00
docs Remove wording indicating proto2 support is reimplemented 2019-09-03 04:24:46 -05:00
editors Improve fix for https://github.com/google/protobuf/issues/295 2017-05-23 15:27:29 +02:00
examples [bazel] Load python rules from @rules_python 2019-08-06 16:50:32 -07:00
java Merge pull request #6568 from ennerf/add-jigsaw-module-name 2019-08-30 13:56:17 -07:00
js Down integrate to GitHub 2019-08-22 17:33:01 -07:00
kokoro adding protoc support for s390x 2019-08-30 11:44:43 -07:00
m4 Mostly fix Sun Studio configuration using SunCC compiler 2018-09-12 22:18:27 -04:00
objectivec Fix typo that snuck in with last commit. 2019-08-30 11:43:08 -04:00
php Fix the issue for parsing zero length message (#6592) 2019-08-30 10:47:25 -07:00
protoc-artifacts adding protoc support for s390x 2019-08-30 11:44:43 -07:00
python Down integrate to GitHub 2019-08-22 17:33:01 -07:00
ruby Merge pull request #6547 from haberman/layout_clear 2019-08-28 15:08:30 -07:00
src GetOrRegisterExtension -> GetOrInitializeExtension 2019-08-23 17:29:59 -05:00
third_party Move six.BUILD to third_party and update paths 2019-08-15 14:53:59 -07:00
util/python [bazel] Add fixes for --incompatible_load_{cc,java,proto}_rules_from_bzl (Part 2) 2019-07-29 14:14:04 -07:00
.gitignore Use parameter name comment 2019-06-26 20:39:03 +02:00
.gitmodules Include googletest as a submodule (#3993) 2018-03-26 13:54:32 -07:00
appveyor.bat use netcoreapp2.1 for testing 2019-03-12 05:16:52 -04: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] Load python rules from @rules_python 2019-08-06 16:50:32 -07:00
build_files_updated_unittest.sh Copy files to temp-dir for testing 2019-07-24 10:23:55 -07:00
CHANGES.txt Merge 3.9.x 201908071359 to master (#6484) 2019-08-09 13:21:18 -07: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 Merge 3.9.x 201908071359 to master (#6484) 2019-08-09 13:21:18 -07:00
CONTRIBUTING.md Update CONTRIBUTING.md 2019-05-31 15:32:02 -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
global.json Bump target frameworks of C# programs from netcoreapp1.0 to netcoreapp2.1 (#5838) 2019-03-11 13:03:58 -07:00
LICENSE Cleanup LICENSE file. 2018-03-26 15:03:41 -07:00
Makefile.am Add GeneratedMessageTest.Proto2.cs to EXTRA_DIST 2019-08-23 17:29:59 -05:00
post_process_dist.sh Removed javanano from post_process_dist.sh 2018-06-05 09:17:19 -07:00
protobuf_deps.bzl bazel: Change zlib URL to GitHub 2019-08-29 11:11:19 -07:00
Protobuf-C++.podspec Add podspec for C++ (#6404) 2019-07-23 13:51:21 -07:00
protobuf-lite.pc.in Libs should not include @PTHREAD_CFLAGS@ 2019-02-22 11:19:38 -08:00
protobuf.bzl [bazel] Load python rules from @rules_python 2019-08-06 16:50:32 -07:00
protobuf.pc.in Down integrate to GitHub 2019-06-11 16:00:16 -07:00
Protobuf.podspec Merge 3.9.x 201908071359 to master (#6484) 2019-08-09 13:21:18 -07:00
README.md Added linkage monitor badge (#6327) 2019-07-01 14:59:15 -07:00
tests.sh compatibility test between last released and current for java python php (#6441) 2019-07-31 17:49:26 -07:00
update_compatibility_version.py compatibility test between last released and current for java python php (#6441) 2019-07-31 17:49:26 -07:00
update_file_lists.sh Add test to verify BUILD- and cmake-files are in sync with src/Makefile.am 2019-07-24 10:23:55 -07:00
update_version.py Merge 3.9.x 201908071359 to master (#6484) 2019-08-09 13:21:18 -07:00
WORKSPACE Remove duplicate six http_archive definition 2019-08-15 14:53:59 -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
Build status
Java java Build status
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
Build status
Build status
Build status
Objective-C objectivec Build status
Build status
Build status
Build status
C# csharp Build status Build status
Build status
JavaScript js Build status Build status
Ruby ruby Build status
Build status
Build status
Build status
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/