Re: [protobuf] proto versioning - preventing linking at runtime to a proto version different than at buildtime

Ah, I see. In that case I think you're right that it would be best to put the symbols in separate namespaces for client and server. The protocol compiler does not have any special support for this, but you could accomplish it by having two .proto files which are identical except that one says

Re: [protobuf] proto versioning - preventing linking at runtime to a proto version different than at buildtime

Thanks for the reply. Unfortunately sharing compiled proto symbols between Client and Server is not an option for me as Client and Server are independently deployable and bump their proto version independently. It sounds like putting the proto symbols in a unique namespace per component would

Re: [protobuf] proto3 beta 3.1 Missing aclocal.m4 File?

On Wed, Jun 22, 2016 at 12:41 PM, Doug Lewis wrote: > I'm trying to build proto3 beta 3.1 using Cygwin. The autogen.sh script > errors out because it cannot find the aclocal file. I see the aclocal.m4 > file in the zip of the previous beta version but I do not see any

[protobuf] proto3 beta 3.1 Missing aclocal.m4 File?

I'm trying to build proto3 beta 3.1 using Cygwin. The autogen.sh script errors out because it cannot find the aclocal file. I see the aclocal.m4 file in the zip of the previous beta version but I do not see any aclocal file in the 3.1 zip. Thanks, Doug -- You received this message because

Re: [protobuf] proto versioning - preventing linking at runtime to a proto version different than at buildtime

I sounds to me like this symbol duplication is causing a C++ ODR (one-definition rule) violation, which could explain the crashes you have seen. I would try moving the compiled proto symbols into a separate library and have both the client and server libs depend on that same library so that there