my rage from v8 is spilling over
Go to file
2021-08-02 20:43:43 -07:00
.github Change 'Sur' to 'sur' to see if that works 2021-06-17 16:36:33 -04:00
benchmarks updating caliper to latest maven version. (#8813) 2021-07-13 15:58:40 -07:00
cmake Move field_access_listener from libprotobuf-lite to libprotobuf (#8775) 2021-06-28 16:07:28 -07:00
conformance Sync from Piper @375548932 2021-05-24 13:49:39 -07:00
csharp [csharp] ByteString.CreateCodedInput should use ArraySegment offset and count 2021-06-18 11:52:53 +12:00
docs Merge pull request #8832 from busunkim96/patch-1 2021-07-26 15:19:00 -07:00
editors
examples
java Remove JvmField annotations from Kotlin private properties (#8804) (#8811) 2021-07-13 15:25:00 -07:00
js remove various broken build status tags 2021-07-29 10:14:29 -04:00
kokoro use our java tests target instead of recursive walk (#8777) 2021-06-28 14:31:56 -07:00
m4
objectivec remove various broken build status tags 2021-07-29 10:14:29 -04:00
php Removed PHP support for third_party/wyhash in favor of ABSL wyhash. 2021-08-02 15:36:53 -07:00
protoc-artifacts Update protobuf version 2021-06-04 21:21:39 +00:00
python remove various broken build status tags 2021-07-29 10:14:29 -04:00
ruby Make the Ruby DSL use a unique filename for each implicit file. 2021-08-02 20:43:43 -07:00
src Merge pull request #8850 from haberman/rubybuilder 2021-08-02 14:50:35 -07:00
third_party Ported Ruby to ABSL wyhash. 2021-08-02 15:32:01 -07:00
util/python
.bazelignore
.gitignore Merge branch 'master' into rubybuilder 2021-07-30 15:04:53 -07:00
.gitmodules
.readthedocs.yml
appveyor.bat
appveyor.yml
autogen.sh Build updates (#5300) 2021-05-17 14:53:27 -07:00
BUILD Update the automake and Bazel configs to be consistent about field_access_listener.cc (#8823) 2021-07-16 12:26:09 -07:00
build_files_updated_unittest.sh
cc_proto_blacklist_test.bzl
CHANGES.txt "big sur" -> "Big Sur". 2021-06-17 16:13:47 -04:00
compiler_config_setting.bzl
composer.json
configure.ac Update protobuf version 2021-06-04 21:21:39 +00:00
CONTRIBUTING.md
CONTRIBUTORS.txt
fix_permissions.sh
generate_changelog.py
generate_descriptor_proto.sh
global.json
internal.bzl
LICENSE
Makefile.am Add new file to Makefile.am. 2021-07-31 13:13:45 -07:00
maven_install.json
post_process_dist.sh
protobuf_deps.bzl Update rules_jvm_external to 4.1 (#8800) 2021-07-08 09:05: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
protobuf.bzl Sync from Piper @375548932 2021-05-24 13:49:39 -07:00
protobuf.pc.in
Protobuf.podspec Update protobuf version 2021-06-04 21:21:39 +00:00
README.md Sync from Piper @375548932 2021-05-24 13:49:39 -07:00
tests.sh Updated Ruby 3.0 test to 3.0.2. 2021-08-01 12:07:15 -07:00
update_compatibility_version.py
update_file_lists.sh
update_version.py Adding protobuf_version.bzl to get updated version in python script 2021-06-25 21:07:31 +00:00
WORKSPACE Removing dependencies and renaming bazel version file 2021-06-21 23:03:51 +00: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/