Google Git
Sign in
flutter / third_party / protobuf / acd5b05e9f1ec2153574807463af0612267b6067
commitacd5b05e9f1ec2153574807463af0612267b6067[log] [tgz]
authorFeng Xiao <xfxyjwf@gmail.com>Thu Aug 09 21:21:01 2018 -0700
committerFeng Xiao <xfxyjwf@gmail.com>Thu Aug 09 21:21:01 2018 -0700
tree7f0d6bee5ea04e9f3e8e8ce9be5b168d5ff5c05d
parent8e4fd1b4e8a1b29faefaff1ce794b7a2f607d994 [diff]
Fix failing tests.

1. Fix C++ tests.
  * Add missing files to Makefile.am and fix distcheck in tests.sh
  * Remove BUILT_SOURCES from conformance/Makefile.am.
  * Add some missing override keyword.
  * Add a type cast to int64 because our StrCat() in stubs can't handle size_t.
2. Fix Java tests.
  * Add missing test dependency on guava in pom.xml.
  * Include newly referenced test data in test resources.
  * Manually fix map_lite_test.proto which is overwritten because it's mapped
    from map_test.proto in google3.
  * Add back "optimize_for = LITE_RUNTIME" which is still needed to keep the
    opensource test passing as it's still running lite tests.
  * Add a type cast in newBuilder() because without it the code doesn't compile
    with openjdk javac 1.8 (the compiler can't figure if it's the right type
    due to complex generic typing).
3. Fix Python tests.
  * Remove/replace references to <hash_map>.
  * Suppress more warnings in setup.py.
  * Replace incorrect header inclusion for google/protobuf/proto_api.h.
  * Add strings::EndsWith to google/protobuf/stubs/strutil.h because it's
    referenced in the updated python C extension code.
  * Replace proto2 with google::protobuf. The proto2 name is leaked to
    opensource because we removed the subsitition rule for proto2 namespace
    but only fixed C++ source code and forgot to update python C extension code.
22 files changed
tree: 7f0d6bee5ea04e9f3e8e8ce9be5b168d5ff5c05d
  1. .github/
  2. benchmarks/
  3. cmake/
  4. conformance/
  5. csharp/
  6. docs/
  7. editors/
  8. examples/
  9. java/
  10. js/
  11. kokoro/
  12. m4/
  13. objectivec/
  14. php/
  15. protoc-artifacts/
  16. python/
  17. ruby/
  18. src/
  19. third_party/
  20. util/
  21. .gitignore
  22. .gitmodules
  23. appveyor.bat
  24. appveyor.yml
  25. autogen.sh
  26. BUILD
  27. CHANGES.txt
  28. composer.json
  29. configure.ac
  30. CONTRIBUTORS.txt
  31. generate_changelog.py
  32. generate_descriptor_proto.sh
  33. LICENSE
  34. Makefile.am
  35. post_process_dist.sh
  36. protobuf-lite.pc.in
  37. protobuf.bzl
  38. protobuf.pc.in
  39. Protobuf.podspec
  40. README.md
  41. six.BUILD
  42. tests.sh
  43. update_file_lists.sh
  44. WORKSPACE
README.md

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/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:

LanguageSourceUbuntuMacOSWindows
C++ (include C++ runtime and protoc)srcBuild statusBuild status
Build status		Build status
JavajavaBuild status
Build status
Build status
PythonpythonBuild status
Build status
Build status		Build status
Build status
Objective-CobjectivecBuild status
Build status
Build status
Build status
C#csharpBuild statusBuild status
JavaScriptjsBuild statusBuild status
RubyrubyBuild statusBuild status
Build status
Gogolang/protobuf
PHPphpBuild status
Build status		Build status
Build status
Dartdart-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/