Google Git
Sign in
flutter / third_party / protobuf / c95ebb7bd8b460956a80bdcb416624c1d5f7eca0
commitc95ebb7bd8b460956a80bdcb416624c1d5f7eca0[log] [tgz]
authorChad Wilson <chadw@thoughtworks.com>Tue Jun 20 09:57:43 2023 -0700
committerCopybara-Service <copybara-worker@google.com>Tue Jun 20 09:59:40 2023 -0700
treef4b295c3349bd55e36695c81cca0164f96a4adc5
parentb2ffbdcfd674d498fe77b0f5ff4ceb199525a0f1 [diff]
deps: Update Guava to 32.0.1 (#13099)

Follow-up from #12953 to update to `32.0.1` to fix an issue on windows:

https://github.com/google/guava/releases/tag/v32.0.1

The underlying issue likely does not affect protobuf as it does not appear to (directly) use the affected `Files.createTempDir` or `FileBackedOutputStream` code which was apparently broken on Windows in `32.0.0`.

Seems best to update anyway.

Closes #13099

COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/13099 from chadlwilson:bump-guava-3201 30bd3f75630aeddb5553810e63dc3ecd38db4333
PiperOrigin-RevId: 541960623
3 files changed
tree: f4b295c3349bd55e36695c81cca0164f96a4adc5
  1. .github/
  2. build_defs/
  3. ci/
  4. cmake/
  5. conformance/
  6. csharp/
  7. docs/
  8. editors/
  9. examples/
  10. java/
  11. objectivec/
  12. php/
  13. pkg/
  14. python/
  15. ruby/
  16. rust/
  17. src/
  18. third_party/
  19. toolchain/
  20. .bazelignore
  21. .bazelrc
  22. .gitignore
  23. .gitmodules
  24. .readthedocs.yml
  25. appveyor.bat
  26. appveyor.yml
  27. BUILD.bazel
  28. CMakeLists.txt
  29. CODE_OF_CONDUCT.md
  30. CONTRIBUTING.md
  31. CONTRIBUTORS.txt
  32. fix_permissions.sh
  33. generate_changelog.py
  34. generate_descriptor_proto.sh
  35. global.json
  36. google3_export_generated_files.sh
  37. LICENSE
  38. maven_install.json
  39. Protobuf-C++.podspec
  40. protobuf.bzl
  41. Protobuf.podspec
  42. protobuf_deps.bzl
  43. protobuf_release.bzl
  44. protobuf_version.bzl
  45. README.md
  46. regenerate_stale_files.sh
  47. SECURITY.md
  48. update_subtrees.sh
  49. version.json
  50. WORKSPACE
README.md

Protocol Buffers - Google's data interchange format

Copyright 2008 Google Inc.

Overview

Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. You can learn more about it in protobuf's documentation.

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 GitHub release page.

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 repository.

These pre-built binaries are only provided for released versions. If you want to use the github main 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:

LanguageSource
C++ (include C++ runtime and protoc)src
Javajava
Pythonpython
Objective-Cobjectivec
C#csharp
Rubyruby
Goprotocolbuffers/protobuf-go
PHPphp
Dartdart-lang/protobuf
JavaScriptprotocolbuffers/protobuf-javascript

Quick Start

The best way to learn how to use protobuf is to follow the tutorials in our developer guide.

If you want to learn from code examples, take a look at the examples in the examples directory.

Documentation

The complete documentation is available at the Protocol Buffers doc site.

Support Policy

Read about our version support policy to stay current on support timeframes for the language libraries.

Developer Community

To be alerted to upcoming changes in Protocol Buffers and connect with protobuf developers and users, join the Google Group.