On Mon, Apr 27, 2015 at 11:04 AM, elodg <[email protected]> wrote: > 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? > Besides these protos, what else do you provide for plug-in developers to code against your framework? Do you provide a static library or put everything as source code? If you provide a static library for plug-in developers to link with, I think you can have the generated .pb.cc files compiled in the static library and include .pb.h in the public header files for plugin developers to use.
> > -- > 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. > -- 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.
