Brak opisu

stone4774 d053271dee Use the first enum value instead of 0 in DefaultValueObjectWriter::FindEnumDefault 8 lat temu
benchmarks 6cd4ec4972 Sync internal benchmark changes 8 lat temu
cmake 724f0be33d Move `compiler/plugin.pb.cc` to libprotobuf with the other WKT sources. 8 lat temu
conformance 39a789e657 Removed using statements from common.h 8 lat temu
csharp 0c52335587 Update .NET SDK to 2.0.3 8 lat temu
docs 0d397a1756 Fix link markup in third party list. 8 lat temu
editors 979107ec7a Improve fix for https://github.com/google/protobuf/issues/295 8 lat temu
examples 35119e39a0 Add a check_protobuf_required_bazel_version() for use in WORKSPACEs 8 lat temu
java 019ceea4b3 Drop java 6 support 8 lat temu
javanano ddc00963c0 Add a notice for nano. 9 lat temu
jenkins 028d6f13ee Add Python 3.5 3.6 8 lat temu
js 383a4941d5 Merge remote-tracking branch 'origin/3.5.x' into master 8 lat temu
kokoro 204a6413d6 Move kokoro macOS builds to to Xcode 9.1. 8 lat temu
m4 4a4c67b6a2 Add std::forward and std::move autoconf check 8 lat temu
more_tests 7db148f92a Add makefile for extended tests to be run before release. 16 lat temu
objectivec 07f023188e Fix up the docs to mention the WKTs generated files also. 8 lat temu
php a48d58df96 Convert descriptortype to type for upb_msgval_sizeof (#4357) 8 lat temu
protoc-artifacts bb40c0c0c4 Merge pull request #4291 from google/3.5.x 8 lat temu
python e34ec6077a Only check filenames when end with .py in _CalledFromGeneratedFile() (#4262) 8 lat temu
ruby bb40c0c0c4 Merge pull request #4291 from google/3.5.x 8 lat temu
src d053271dee Use the first enum value instead of 0 in DefaultValueObjectWriter::FindEnumDefault 8 lat temu
third_party 7f1491506c upgrade submodule 8 lat temu
util 985c968443 Remove hack for building Python support with Bazel. 10 lat temu
.gitignore 23adfeb003 Reserve unknown in Ruby (#3763) 8 lat temu
.gitmodules a289d43608 Added C++ benchmark. (#1525) 9 lat temu
.travis.yml 0c52335587 Update .NET SDK to 2.0.3 8 lat temu
BUILD 350b135e23 Blacklist all WELL_KNOWN_PROTOS from Bazel C++ code generation. 8 lat temu
CHANGES.txt 7bf1e1919a Update changelog 8 lat temu
CONTRIBUTORS.txt 49bc8c0963 Add nano proto authors and update LICENSE file to include Android.mk. 11 lat temu
LICENSE 2a50e67c78 Add support for POWER Linux 10 lat temu
Makefile.am 383a4941d5 Merge remote-tracking branch 'origin/3.5.x' into master 8 lat temu
Protobuf.podspec 050fc9a437 Update version number to 3.5.1 8 lat temu
README.md 74bf45f379 Add bazel support for examples. 8 lat temu
WORKSPACE 699c0eb9cf bazel: Add proto_library rules for well known types. Fixes #2763 8 lat temu
appveyor.bat f26e8c2ae0 Convert C# projects to MSBuild (csproj) format 8 lat temu
appveyor.yml f26e8c2ae0 Convert C# projects to MSBuild (csproj) format 8 lat temu
autogen.sh f4ff17bb16 Update autogen.sh 8 lat temu
composer.json 21b0e5587c Update PHP descriptors (#3391) 8 lat temu
configure.ac a3868af12b Merge pull request #4131 from pherl/merge 8 lat temu
generate_changelog.py 277a8b6580 generate_changelog.py: flush output so piping works correctly. 9 lat temu
generate_descriptor_proto.sh 09354db143 Merge from Google internal for 3.4 release 8 lat temu
gmock.BUILD 1327e6f470 Update repo to use google test 9 lat temu
post_process_dist.sh 1ec45f81ef Add protobuf-all in post release 8 lat temu
protobuf-lite.pc.in 37e7a3c4b8 Uncomment conflict fields from pkg-config files. 10 lat temu
protobuf.bzl 35119e39a0 Add a check_protobuf_required_bazel_version() for use in WORKSPACEs 8 lat temu
protobuf.pc.in 37e7a3c4b8 Uncomment conflict fields from pkg-config files. 10 lat temu
six.BUILD 29799238c2 Add srcs_version = "PY2AND3" in BUILD files 10 lat temu
tests.sh bb40c0c0c4 Merge pull request #4291 from google/3.5.x 8 lat temu
update_file_lists.sh 2e4c52a096 `update_file_lists.sh` depends on Bash features, thus needs Bash sebang. 8 lat temu

README.md

Protocol Buffers - Google's data interchange format

Build Status Build status Build Status 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:

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
JavaNano javanano
JavaScript js
Ruby ruby
Go golang/protobuf
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/