Suppose there is a plug-in framework that uses protobuf to pass data around between plug-ins. The plug-ins can be C++ dynamic libraries, where the proto wire crosses the ABI boundary going around binary incompatibilities. Many different predefined protos exist that need to be distributed to plug-in developers. I think I am correct in saying that since there is no guarantee of ABI compatibility, each plug-in dll will need to compile and statically link protobuf. The question is how is the library and protos meant to be distributed? Do I provide .protos and let plug-in developers download protobuf and compile everything? Do I provide pb.c/h and protobuf library sources?
-- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
