Dears,
we have a rpc.proto built inside our core framework, built as a DLL.
Other protos contain extension to base message defined in rpc.proto,
and they are built in separate and different executables.
The MSVC linker compains for error since the RpcMessage class (defined
in rpc.proto) and
If you invoke protoc like:
protoc --cpp_out=dllexport_decl=MY_EXPORT_MACRO:path/to/output/dir
myproto.proto
then it will generate code with MY_EXPORT_MACRO in all the right places.
However, this option is incomplete -- currently there is no way to force
the generated .pb.h to #include a header
We currently get around this limitation by forcing the the header to
be included using compiler command line flags:
Windows: /FIproject/Config.h
Linux: -include project/Config.h
-Aron
On Tue, Sep 22, 2009 at 11:37 AM, Kenton Varda ken...@google.com wrote:
If you invoke protoc like:
protoc
Summary: I would really like to be able to iterate through the message
descriptors in a DescriptorPool, in particular the generated_pool.
I am sending various protocol buffers as messages across a transport.
On the receiving side of the transport, I need to use information
contained in a message
Hi,
On Tue, Sep 22, 2009 at 15:39, Exaurdon alexrichard...@gmail.com wrote:
Summary: I would really like to be able to iterate through the message
descriptors in a DescriptorPool, in particular the generated_pool.
I am sending various protocol buffers as messages across a transport.
On the
In a limited scope, this would probably work.
In my particular case I am working with teams from 10+ different
projects. Each project is generating dozens to hundreds of messages. I
imagine that trying to get all of those messages into a single message
would result in a pretty bloated message
