Can custom option be set to repeated?
sample code
syntax = "proto3";
package sample;
import "google/protobuf/descriptor.proto";
extend google.protobuf.FieldOptions {
Scope scope = 5;
}
message Scope {
repeated string type = 1;
}
message Sample {
uint64 id = 1 [
(scope) = {
David,
Thank you for your very prompt reply! I am required (for
compatibility) to use version 2.6.0. I'm not sure this makes much of a
difference. What I am attempting to ultimately accomplish is turn the
.proto files into code I can feed into the PowerPC cross compiler to
generate code as
The fundamental unit for protobufs (across all serialization and
presentation formats, including JSON) is a message.
The semantics of the general JSON format do not map to protobuf semantics
very well, but the proto3 language guide has a section on the JSON
structures that can interoperate
(I think Kerry's reply went to a different thread...)
On Thursday, April 23, 2020 at 5:11:05 PM UTC-7, Crouse, Kerry wrote:
>
> David,
>
> Thank you for your very prompt reply! I am required (for
> compatibility) to use version 2.6.0. I'm not sure this makes much of a
> difference. What I
It looks like this:
types: ["1"]
should be:
type: ["1"]
Does that change fix the error?
On Thursday, April 23, 2020 at 7:16:31 PM UTC-7, mustache_master wrote:
>
>
> Can custom option be set to repeated?
>
> sample code
> syntax = "proto3";
>
> package sample;
>
> import
I have been through the online documentation, readmes, and protoc help and
I'm missing how to do this: generate big endian protobuf code on little
endian machine. Can someone point me to a howto? My build machine is a
Linux Debian x86 machine. My target machine is a 32 bit PowerPC device.
(I'm assuming this is for C++...)
The protobuf libraries (including the code generated by the protobuf
compiler) should internally contain the necessary #ifdef/etc. guards to
handle endian issues. For example:
