cf12bffd9d
This likely should have been the default from the start, as without it is way to common to get symbol collisions between different proto files. It would be nice to support a "migration" mode where both names are created to aid it moving code to this model, but with ObjC `@class` decls being very common to avoid header imports to control rebuilds/etc., it doesn't work as an `@class` usage will error if one also uses `@compatibility_alias`. Falling back to `#define` the two together also doesn't work as the header with the `@class` will cause methods to get defined with one interface, but when methods taking those types are define will likely #import the generate header and thus get the define and end up with a different signature. So for now, there is no migration support and code has to be updated in one shot with enable the new prefixing. - Add a generation option to enable this change in generation. - Add a second generation option to provide a list of proto package that are exceptions from using the proto package. This allows easier migration/updating of code one package at a time. |
||
|---|---|---|
| .github | ||
| benchmarks | ||
| cmake | ||
| conformance | ||
| csharp | ||
| docs | ||
| editors | ||
| examples | ||
| java | ||
| js | ||
| kokoro | ||
| m4 | ||
| objectivec | ||
| php | ||
| protoc-artifacts | ||
| python | ||
| ruby | ||
| src | ||
| third_party | ||
| util/python | ||
| .bazelignore | ||
| .gitignore | ||
| .gitmodules | ||
| .readthedocs.yml | ||
| appveyor.bat | ||
| appveyor.yml | ||
| autogen.sh | ||
| BUILD | ||
| build_files_updated_unittest.sh | ||
| cc_proto_blacklist_test.bzl | ||
| CHANGES.txt | ||
| compiler_config_setting.bzl | ||
| composer.json | ||
| configure.ac | ||
| CONTRIBUTING.md | ||
| CONTRIBUTORS.txt | ||
| fix_permissions.sh | ||
| generate_changelog.py | ||
| generate_descriptor_proto.sh | ||
| global.json | ||
| internal.bzl | ||
| LICENSE | ||
| Makefile.am | ||
| maven_install.json | ||
| post_process_dist.sh | ||
| protobuf_deps.bzl | ||
| Protobuf-C++.podspec | ||
| protobuf-lite.pc.in | ||
| protobuf.bzl | ||
| protobuf.pc.in | ||
| Protobuf.podspec | ||
| README.md | ||
| tests.sh | ||
| update_compatibility_version.py | ||
| update_file_lists.sh | ||
| update_version.py | ||
| WORKSPACE | ||
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: