[protobuf] Message was missing required fields

2010-04-16 Thread SyRenity
Hi. I'm getting occasionally the following error below in my Java app: com.google.protobuf.InvalidProtocolBufferException: Message was missing required fields. (Lite runtime could not determine which fields were missing). at

[protobuf] Re: Placing byte buffer into string

2010-02-14 Thread SyRenity
Thanks. On Feb 15, 12:25 am, Evan Jones ev...@mit.edu wrote: On Feb 14, 2010, at 17:23 , SyRenity wrote: Actually, answering myself it seems to be as simple as:   sData.assign(buffer, size); //Where size is the full buffer size Yes, that works. See the following for more help: http

Re: Fwd: [protobuf] Re: Cross-compiling protobuf to 32-bit

2010-02-01 Thread SyRenity
Hi. Any idea of the issue below? I'm currently using static libraries compiled on another (virtual) 32- bit machine, which seems to be working fine, but I really would prefer a native solution. Regards. On Jan 29, 11:28 pm, Stas Oskin stas.os...@gmail.com wrote: Sorry, forwarding to list as

[protobuf] Getting empty strings from protobuf

2010-01-28 Thread SyRenity
Hi. I'm trying to use protobuf for cross-platform, cross-architecture communication - Java 64-bit to C++ 32-bit. The integer data is passed fine - problem is in the strings, which are coming empty. Used version is 2.3, lite (for faster speed). Any idea? Thanks! -- You received this message

[protobuf] Cross-compiling protobuf to 32-bit

2010-01-28 Thread SyRenity
Hi. I'm trying to compile a 32-bit protobuf on 64-bit machine. No matter what I tried (changing build option, host option or setting - m32 flag), I couldn't get it working. Either I stuck on compile stage, or the resulting binaries are 64-bit. I do able to compile other apps via -m32 flag. (I

Communication methods

2009-05-24 Thread SyRenity
Hi. Sorry if this was already asked in the past, but does Protocol Buffers provide some IPC communication methods? Or they provide the data encapsulation, and I should use any method I want? Regards. --~--~-~--~~~---~--~~ You received this message because you