Google Git
Sign in
pigweed / third_party / github / protocolbuffers / protobuf / 8257c4469d065eac17b2e310e8e2086cc93f4505
commit8257c4469d065eac17b2e310e8e2086cc93f4505[log] [tgz]
authorProtobuf Team Bot <protobuf-github-bot@google.com>Wed Apr 10 00:33:05 2024 -0700
committerCopybara-Service <copybara-worker@google.com>Wed Apr 10 00:35:29 2024 -0700
treeaf299d4a387610a4b7fb9a926e92e97817ef0bd8
parenta94f57bd69e9a5999ba67736e4d70a9d7f96aaf5 [diff]
Copy py_proto_library from rules_python to protobuf

https://github.com/bazelbuild/rules_python/blob/main/python/private/proto/py_proto_library.bzl

Contributors:
d96214f tpudlik@google.com      Wed Nov 15 02:48:06 2023 -0800  fix: py_proto_library: transitive strip_import_prefix (#1558)
85e50d2 tpudlik@gmail.com       Tue Nov 14 06:04:59 2023 -0800  fix: py_proto_library: append to PYTHONPATH less (#1553)
bee35ef zplin@uber.com  Wed Oct 11 20:59:34 2023 -0700  fix: allowing to import code generated from proto with strip_import_prefix (#1406)
1a333ce ilist@google.com        Tue Jun 20 19:36:39 2023 +0200  fix: plugin_output in py_proto_library rule (#1280)
6905e63 ignas.anikevicius@woven-planet.global   Sat Feb 11 14:02:33 2023 +0900  fix: make py_proto_library respect PyInfo imports (#1046)
0d3c4f7 ilist@google.com        Wed Jan 18 23:15:52 2023 +0000  Implement py_proto_library (#832)
PiperOrigin-RevId: 623401031
4 files changed
tree: af299d4a387610a4b7fb9a926e92e97817ef0bd8
  1. .bcr/
  2. .github/
  3. bazel/
  4. benchmarks/
  5. build_defs/
  6. ci/
  7. cmake/
  8. conformance/
  9. csharp/
  10. docs/
  11. editors/
  12. examples/
  13. java/
  14. lua/
  15. objectivec/
  16. php/
  17. pkg/
  18. protos/
  19. protos_generator/
  20. python/
  21. ruby/
  22. rust/
  23. src/
  24. third_party/
  25. toolchain/
  26. upb/
  27. upb_generator/
  28. .bazelignore
  29. .bazelrc
  30. .clang-format
  31. .gitignore
  32. .gitmodules
  33. .readthedocs.yml
  34. appveyor.bat
  35. appveyor.yml
  36. BUILD.bazel
  37. Cargo.bazel.lock
  38. Cargo.lock
  39. CMakeLists.txt
  40. CODE_OF_CONDUCT.md
  41. CONTRIBUTING.md
  42. CONTRIBUTORS.txt
  43. fix_permissions.sh
  44. generate_descriptor_proto.sh
  45. global.json
  46. google3_export_generated_files.sh
  47. LICENSE
  48. maven_install.json
  49. MODULE.bazel
  50. PrivacyInfo.xcprivacy
  51. Protobuf-C++.podspec
  52. protobuf.bzl
  53. Protobuf.podspec
  54. protobuf_deps.bzl
  55. protobuf_release.bzl
  56. protobuf_version.bzl
  57. README.md
  58. regenerate_stale_files.sh
  59. SECURITY.md
  60. version.json
  61. WORKSPACE
README.md

Protocol Buffers - Google's data interchange format

OpenSSF Scorecard

Copyright 2023 Google LLC

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.

Working With Protobuf Source Code

Most users will find working from supported releases to be the easiest path.

If you choose to work from the head revision of the main branch your build will occasionally be broken by source-incompatible changes and insufficiently-tested (and therefore broken) behavior.

If you are using C++ or otherwise need to build protobuf from source as a part of your project, you should pin to a release commit on a release branch.

This is because even release branches can experience some instability in between release commits.

Protobuf Compiler Installation

The protobuf 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.