Comment #4 on issue 128 by ssj...@gmail.com: Can not dlopen a library using  
a protobuf message twice
http://code.google.com/p/protobuf/issues/detail?id=128

I can's try the second advise set "option optimize_for = LITE_RUNTIME;" as  
I need to use protobuf's descriptor and reflection，does the first advice  
really works? you say "probably"

Comment #5 on issue 128 by ken...@google.com: Can not dlopen a library  
using a protobuf message twice
http://code.google.com/p/protobuf/issues/detail?id=128

Statically linking libprotobuf into your dynamic library will work as long  
as protobufs are entirely encapsulated within your library's implementation  
and not exposed in the interface.  It may be a little tricky to convince  
gcc to link libprotobuf statically without linking everything statically,  
but it should be doable -- I think it works if you explicitly pass  
libprotobuf.a on the command line instead of the usual "-lprotobuf".

Comment #6 on issue 128 by richardg...@gmail.com: Can not dlopen a library  
using a protobuf message twice
http://code.google.com/p/protobuf/issues/detail?id=128

This assert causes problems even if you do not intend to unload the dynamic  
library, as it occurs on dlopen. Is it strictly necessary? Can it be  
replaced with an assert when the message definitions are different?

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings