Google Git
Sign in
pigweed / third_party / github / protocolbuffers / protobuf / f1998d91a8155b0935ae95e8abb29e7fd21397bf
commitf1998d91a8155b0935ae95e8abb29e7fd21397bf[log] [tgz]
authorAdam Cozzette <acozzette@google.com>Wed Nov 09 06:55:38 2022 -0800
committerCopybara-Service <copybara-worker@google.com>Wed Nov 09 06:57:08 2022 -0800
tree6b6447edfb712607017688ee2ba593f1e0298c8c
parent9b81aaae58be0a4db4c06180042e035c383c7e90 [diff]
Update auto-generation script to handle well-known types

I went ahead and deleted the update_file_list.sh script, because (a)
there was no good reason for it to be in a separate script and (b) we
now need to handle the well-known types in addition to file_lists.cmake.
With this change, we just invoke the staleness tests from the main
script to update everything.

While I was at it I made a couple small fixes:
- Don't skip the update step just because the previous commit was by
  "Protobuf Team Bot". Copybara commits use this name and we still want
  to do the auto-update step after them.
- Include the CL number in the description if the previous commit came
  from a CL.

PiperOrigin-RevId: 487231324
5 files changed
tree: 6b6447edfb712607017688ee2ba593f1e0298c8c
  1. .github/
  2. build_defs/
  3. cmake/
  4. conformance/
  5. csharp/
  6. docs/
  7. editors/
  8. examples/
  9. java/
  10. kokoro/
  11. objectivec/
  12. php/
  13. pkg/
  14. python/
  15. ruby/
  16. src/
  17. third_party/
  18. toolchain/
  19. .bazelignore
  20. .bazelrc
  21. .gitignore
  22. .gitmodules
  23. .readthedocs.yml
  24. appveyor.bat
  25. appveyor.yml
  26. BUILD.bazel
  27. CHANGES.txt
  28. CMakeLists.txt
  29. CONTRIBUTING.md
  30. CONTRIBUTORS.txt
  31. fix_permissions.sh
  32. generate_changelog.py
  33. generate_descriptor_proto.sh
  34. global.json
  35. LICENSE
  36. maven_install.json
  37. Protobuf-C++.podspec
  38. protobuf.bzl
  39. Protobuf.podspec
  40. protobuf_deps.bzl
  41. protobuf_release.bzl
  42. protobuf_version.bzl
  43. push_auto_update.sh
  44. README.md
  45. SECURITY.md
  46. version.json
  47. 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/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 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:

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/

Developer Community

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