| commit | f95db86cc80c80e946c193c4a54236e5f873ea47 | [log] [tgz] |
|---|---|---|
| author | Greg Pataky <gregpataky@google.com> | Thu Jun 22 20:04:36 2023 +0000 |
| committer | Greg Pataky <gregpataky@google.com> | Mon Jun 26 22:15:13 2023 +0000 |
| tree | 92befe4ac0504e525e215d9771a547b164e13c23 | |
| parent | b5b8b11fb16c7c72c1e4b26cd029953d2a5c37cd [diff] |
external/protobuf: Correct depfile generation when there are no outputs Prevents the compiler from generating a malformed depfile if an input file did not lead to any meaningful generation. This is an edge case that is not exercised often. I discovered `protoc` outputs a malformed depfile if you run it on a `proto` file that has no associated `output_filenames`. This was found using the Android Soong `"grpc-java-plugin"` proto generation plugin that only outputs a gRPC Java source if the input `proto` has a `service` definition. Reasonably, there could be shared proto files that get invoked for gRPC generation that are meant as shared types for `service` files, but do not define one themselves. There is a workaround to edit `srcs` passed to Soong, but this removes that requirement. Cherry picked from upstream: https://github.com/protocolbuffers/protobuf/commit/a44fc2b063d7466d48e2aeba05f9c35654140d87 Test: Built using `lunch aosp_arm-eng; m`. Bug: b/287536219 Change-Id: I623ba695b9d1ef955f73599f65c4b695c70e7630
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 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 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 |
|---|---|
| C++ (include C++ runtime and protoc) | src |
| Java | java |
| Python | python |
| Objective-C | objectivec |
| C# | csharp |
| Ruby | ruby |
| Go | protocolbuffers/protobuf-go |
| 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: