This worked, thanks Nadav!
On Monday, December 2, 2019 at 7:49:50 PM UTC-8, Nadav Samet wrote:
>
> Hi Yuri,
>
> Try this:
>
> protoc --include_imports --descriptor_set_out=/dev/stdout file1.proto
> fie2.proto ... | protoc --decode=google.protobuf.FileDescriptorSet
>
Just tried it out. Seems to grab everything!
On Tuesday, December 3, 2019 at 10:35:29 AM UTC-8, John Krzemien wrote:
>
> Won't this only give the 1st level of dependencies? He'll likely need the
> transitive closure if he's trying to generate and build.
>
> On Monday, December 2, 2019 at 7:49:50
--include_imports should make protoc provide the full transitive closure.
On Tue, Dec 3, 2019 at 10:35 AM John Krzemien wrote:
> Won't this only give the 1st level of dependencies? He'll likely need the
> transitive closure if he's trying to generate and build.
>
> On Monday, December 2, 2019
Won't this only give the 1st level of dependencies? He'll likely need the
transitive closure if he's trying to generate and build.
On Monday, December 2, 2019 at 7:49:50 PM UTC-8, Nadav Samet wrote:
>
> Hi Yuri,
>
> Try this:
>
> protoc --include_imports --descriptor_set_out=/dev/stdout
Hi Yuri,
Try this:
protoc --include_imports --descriptor_set_out=/dev/stdout file1.proto
fie2.proto ... | protoc --decode=google.protobuf.FileDescriptorSet
google/protobuf/descriptor.proto | grep "^ name: "
On Mon, Dec 2, 2019 at 7:30 PM Yuri Vic wrote:
> On Sunday, December 1, 2019 at
On Sunday, December 1, 2019 at 11:53:01 AM UTC-8, Marc Gravell wrote:
>
> Untested, but can't you just use protoc with the descriptor-set mode to
> build a FileDescriptorSet (IIRC) which will be the processed output of
> protoc's efforts? Then parse it using the details from descriptor.proto,
>
Untested, but can't you just use protoc with the descriptor-set mode to
build a FileDescriptorSet (IIRC) which will be the processed output of
protoc's efforts? Then parse it using the details from descriptor.proto,
and see what descriptors are in the FileDescriptorSet?
--
You received this
