my rage from v8 is spilling over
Go to file
2021-08-03 12:25:42 -07:00
.github Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
benchmarks Merge tag 'refs/tags/sync-piper' into sync-stage 2021-08-03 12:25:42 -07:00
cmake Merge tag 'refs/tags/sync-piper' into sync-stage 2021-08-03 12:25:42 -07:00
conformance Sync from Piper @375548932 2021-05-24 13:49:39 -07:00
csharp Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
docs Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
editors Spell check only comments and strings in vim 2020-10-27 10:15:05 -07:00
examples Sync from Piper @371422642 2021-04-30 16:12:50 -07:00
java Merge tag 'refs/tags/sync-piper' into sync-stage 2021-08-03 12:25:42 -07:00
js Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
kokoro Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
m4 Updated ax_pthread.m4 to its most recent upstream version 2020-11-20 16:36:56 -08:00
objectivec Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
php Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
protoc-artifacts Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
python Merge tag 'refs/tags/sync-piper' into sync-stage 2021-08-03 12:25:42 -07:00
ruby Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
src Merge tag 'refs/tags/sync-piper' into sync-stage 2021-08-03 12:25:42 -07:00
third_party cleaning up 2021-03-31 16:54:01 +00: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
.bazelignore [bazel] Update gtest and deprecate //external:{gtest,gtest_main} (#7237) 2020-03-02 15:15:22 -08:00
.gitignore Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
.gitmodules Include googletest as a submodule (#3993) 2018-03-26 13:54:32 -07:00
.readthedocs.yml python: publish sphinx docs to read the docs 2020-02-28 13:36:50 -06: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 Build updates (#5300) 2021-05-17 14:53:27 -07:00
BUILD Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
build_files_updated_unittest.sh Fixed sort ordering and updated test to output context information. 2021-04-16 08:10:49 -07:00
cc_proto_blacklist_test.bzl [bazel] Fix blacklisted_protos in cc_toolchain and add test (#7075) 2020-01-15 10:27:35 -08:00
CHANGES.txt Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
compiler_config_setting.bzl [bazel] Move Java runtime/toolchains into //java (#7190) 2020-02-13 13:04:14 -08:00
composer.json Update PHP descriptors (#3391) 2017-08-04 16:35:22 -07:00
configure.ac Update protobuf version 2021-06-04 21:21:39 +00: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
fix_permissions.sh Set execute bit on files if and only if they begin with (#!). (#7347) 2020-04-01 15:28:25 -07:00
generate_changelog.py Replace repo links. 2018-08-22 11:55:30 -07:00
generate_descriptor_proto.sh Updated version to 3.12.3 and updated CHANGES.txt. (#7580) 2020-06-01 13:36:50 -07:00
global.json Improve WriteString perf with SIMD 2021-02-04 07:26:34 +13:00
internal.bzl Bazel powered Java testing (#8506) 2021-04-20 11:36:32 -07:00
LICENSE Cleanup LICENSE file. 2018-03-26 15:03:41 -07:00
Makefile.am Revert "Removed obsolete file from Makefile.am." 2021-08-02 20:47:40 -07:00
maven_install.json rely on only HTTPS mirrors for maven. (#8526) 2021-04-22 12:12:41 -07:00
post_process_dist.sh Removed javanano from post_process_dist.sh 2018-06-05 09:17:19 -07:00
protobuf_deps.bzl Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
protobuf_version.bzl Removing dependencies and renaming bazel version file 2021-06-21 23:03:51 +00:00
Protobuf-C++.podspec Update protobuf version 2021-06-04 21:21:39 +00:00
protobuf-lite.pc.in Libs should not include @PTHREAD_CFLAGS@ 2019-02-22 11:19:38 -08:00
protobuf.bzl Sync from Piper @375548932 2021-05-24 13:49:39 -07:00
protobuf.pc.in Down integrate to GitHub 2019-06-11 16:00:16 -07:00
Protobuf.podspec Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
README.md Sync from Piper @375548932 2021-05-24 13:49:39 -07:00
tests.sh Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
update_compatibility_version.py Merge 3.11.0-rc1 changes to master (#6917) 2019-11-20 18:03:29 -08: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 Sync from Piper @388508285 2021-08-03 11:58:05 -07:00
WORKSPACE Sync from Piper @388508285 2021-08-03 11:58:05 -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
C++ (include C++ runtime and protoc) src
Java java
Python python
Objective-C objectivec
C# csharp
JavaScript js
Ruby ruby
Go protocolbuffers/protobuf-go
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/