my rage from v8 is spilling over
Go to file
Adam Cozzette 3b08c721b8
Comment out unused variable in repeated_field_unittest.cc (#8578)
The test assertion is commented out, but this is causing some warnings
about an unused variable. This commit comments out the variable to fix
that problem.
2021-05-07 08:32:35 -07:00
.github Sync from Piper @371422642 2021-04-30 16:12:50 -07:00
benchmarks Removed file that was mistakenly re-introduced. 2021-05-04 15:50:02 -07:00
cmake Merge pull request #8272 from deannagarcia/kotlinProtos 2021-04-21 10:29:26 -07:00
conformance Bazel powered Java testing (#8506) 2021-04-20 11:36:32 -07:00
csharp Sync from Piper @371422642 2021-04-30 16:12:50 -07:00
docs Update third_party.md (#8511) 2021-04-19 11:16:36 -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-04-30 16:12:51 -07:00
js Merge branch 'master' into sync-stage 2021-05-04 15:49:27 -07:00
kokoro Merge pull request #8536 from shaod2/update-python-docs-script 2021-05-05 16:47:31 -05:00
m4 Updated ax_pthread.m4 to its most recent upstream version 2020-11-20 16:36:56 -08:00
objectivec Move the class map to a CFDictionary. 2021-02-22 13:08:32 -05:00
php Updated and simplified PHP testing structure (#8558) 2021-05-04 10:19:22 -07:00
protoc-artifacts Merge branch '3.15.x' into merge-3-15-x 2021-04-08 10:54:02 -07:00
python Fix constness issue detected by MSVC standard conforming mode (#8568) 2021-05-06 09:09:22 -07:00
ruby fix(ruby): Fix crash when calculating Message hash values on 64-bit Windows (#8565) 2021-05-06 09:45:11 -07:00
src Comment out unused variable in repeated_field_unittest.cc (#8578) 2021-05-07 08:32:35 -07:00
third_party Ported Ruby extension to upb_msg (#8184) 2021-01-13 12:16:25 -08: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 Add 'java/lite/target' to .gitignore (#8439) 2021-03-31 11:03:01 -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 Add cpp tests under release docker image. 2018-07-15 16:41:25 -07:00
BUILD Sync from Piper @371422642 2021-04-30 16:12:50 -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 Updated changelog. 2021-04-30 16:20:39 -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 Merge branch '3.15.x' into merge-3-15-x 2021-04-08 10:54:02 -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
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 Updated and simplified PHP testing structure (#8558) 2021-05-04 10:19:22 -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 @371422642 2021-04-30 16:12:50 -07:00
Protobuf-C++.podspec Updated version to 3.15.8 (#8463) 2021-04-07 15:38:38 -07:00
protobuf-lite.pc.in Libs should not include @PTHREAD_CFLAGS@ 2019-02-22 11:19:38 -08:00
protobuf.bzl Sync from Piper @371422642 2021-04-30 16:12:50 -07:00
protobuf.pc.in Down integrate to GitHub 2019-06-11 16:00:16 -07:00
Protobuf.podspec Updated version to 3.15.8 (#8463) 2021-04-07 15:38:38 -07:00
README.md Update kokoro badge bucket to protobuf-kokoro-badges (#8138) 2020-12-14 10:48:17 -08:00
tests.sh Remove Python compatibility tests (#8570) 2021-05-05 13:02:38 -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 Tweaked update_version.py to leave PHP notes blank 2020-08-21 16:33:52 -07:00
WORKSPACE Sync from Piper @371422642 2021-04-30 16:12:50 -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
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 protocolbuffers/protobuf-go
PHP php Build status
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/