| commit | 3bc2bb9b29375590453d3ebbd6f5b265613d351c | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Wed Sep 11 18:00:16 2019 +0000 |
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Wed Sep 11 18:00:16 2019 +0000 |
| tree | a41056379107d3928a1ca0df4fe35611d64b244a | |
| parent | 311d9e1f7e8967e881d0fe038b81cdf900f476cd [diff] | |
| parent | f609a27b2eb42f1dde7c26dce95174f9ef95a498 [diff] |
Merge changes from topic "protobuf-3.9.1" * changes: Version vendor libprotobuf-cpp-* libraries Add missing override to ~GeneratedExtensionFinder() Fix unused parameter warning in clang with NDEBUG UPSTREAM: Fix unused-parameter clang warnings in arena.h and map_type_handler.h Remove libprotobuf-cpp-*-rtti modules Autodetect rtti Compile javanano as a plugin Restore javanano files that were removed upstream Revert "Wrap liblog dependency in GOOGLE_PROTOBUF_MIN_LOG_LEVEL" Update stubs Update javamicro to compile against v3.9.1 Update Android.bp to match BUILD Add METADATA file and make NOTICE a symlink to LICENSE Rerun configure Merge tag 'v3.9.1' into master Re-apply merge of tag v3.5.2 Revert "Backport upstream changes to allow printing field names verbatim." Revert "Remove 2 usage of isspace as they are not stl port compatible" Revert "Use GOOGLE_CHECK Macro for validation" Revert "Emit macros with proper parentheses." Revert "Generate syntactically correct java for imports from classes with no packages." Revert "Fix some unused parameter warnings" Revert "protobuf: work around a static analyzer bug" Revert "Suppress clang-analyzer-core.uninitialized.UndefReturn warning."
Copyright 2008 Google Inc.
https://developers.google.com/protocol-buffers/
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.
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 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 |    |   | |
| Java | java |    | ||
| Python | python |               |    |  |
| Objective-C | objectivec |     | ||
| C# | csharp |  |  | |
| JavaScript | js |  |  | |
| Ruby | ruby |      |      | |
| Go | golang/protobuf | |||
| PHP | php |   |   | |
| Dart | dart-lang/protobuf |  |
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.
The complete documentation for Protocol Buffers is available via the web at: