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 <yuriv...@gmail.com> wrote: > 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, >> and see what descriptors are in the FileDescriptorSet? >> > > > Doesn't this require building another app just to parse the > FileDescriptorSet file? > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to protobuf+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/protobuf/08957a5c-7821-47ba-8db7-d7b39a7c0ea0%40googlegroups.com > <https://groups.google.com/d/msgid/protobuf/08957a5c-7821-47ba-8db7-d7b39a7c0ea0%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- -Nadav -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to protobuf+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/protobuf/CANZcNErnpO7TT1-HBeFCxvkNLj%2BqAwq1A%3DOqO_D17rUXA5D0eQ%40mail.gmail.com.
