Hello Everyone!

I'm quite new in the world of Protobuf and currently I have forced a 
problem with debugging of application with messages generated based on 
message-lite concept. Lack of reflection mechanisms in an implementation of 
google::protobuf::MessageLite class makes finding out which of the 
parameters of the message was not set as expected is quite hard. Because 
the application runs on the embedded system with limited amount of space, 
we have chosen lightweight version of library, so every single proto 
message definition has defined additional option optimize_for = 
LITE_RUNTIME. Nonetheless on test environment we have no such limitation, 
and the full version would be appreciated. I wonder if there is any way to 
make that option dependent on the compilation target?
Thanks in advance.

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 protobuf+unsubscr...@googlegroups.com.
To post to this group, send email to protobuf@googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to