Thanks all. On Tue, Jun 6, 2017 at 4:42 PM, KarrokDC <dennis.cappend...@gmail.com> wrote:
> Best practice would probably be to incorporate the generation from proto > into cmake (or other build system) to ensure you're always up to date. > > This way you have a good chance (not 100% foolproof) that compilation will > start throwing errors after a .proto update if the code using it is not > updated. > As opposed to someone changing a proto and not the using code, wondering > why things aren't working ;-) > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Protocol Buffers" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/protobuf/xcTEaNboQGc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > protobuf+unsubscr...@googlegroups.com. > To post to this group, send email to protobuf@googlegroups.com. > Visit this group at https://groups.google.com/group/protobuf. > For more options, visit https://groups.google.com/d/optout. > -- 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 post to this group, send email to protobuf@googlegroups.com. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
