I'm using Visual Studio 2008 with STLPort 5.2.0 and the Windows Mobile
5 R2 SDK to compile protobuf-2.2.0. I was able to compile libprotobuf-
lite.lib without much difficulty and protoc.exe has no issue compiling
my proto file:
option optimize_for = LITE_RUNTIME;
message RCMessage {
Hello,
I try to compile protobuf for Windows CE (ARM4I) and I stumbled upon a
compilation error
error C2059 : Syntax error : ')' in extension_set.cc.
After some research i found out that the define OPTIONAL is not
existent for windows ce.
Can somebody help me with this define?
Can someone
Are you sure the problem isn't simply that you've enabled certain pedantic
warnings? I strongly doubt that GCC 4.4 actually requires explicit
initialization of superclasses as this would break lots and lots of code.
On Fri, Oct 30, 2009 at 10:13 AM, Oleg Smolsky o...@smolsky.net wrote:
Hey
Hi,
Using the Java API, when attempting to parse a text-formatted protobuf
message that contains adjacent strings that are meant to be
concatenated, such as in the following contrived example:
name:John Smith
profession:mailman
description:
all these strings
are concatenated
I've found that if I don't use STLPort, it works fine. Which is
unfortunate because I need STLPort for Boost to work under WinCE!
Any thoughts on how to get STLPort to work nicely with Protocol
Buffers?
Thanks,
PaulH
On Oct 30, 10:45 am, PaulH paul.h...@gmail.com wrote:
I'm using Visual Studio
On Fri, Oct 30, 2009 at 10:36 AM, PaulH paul.h...@gmail.com wrote:
OPTIONAL is already defined in windef.h. At the top of
extension_set.cc, add this:
#ifdef UNDER_CE
#ifdef OPTIONAL
#undef OPTIONAL
#endif
#endif
Or you can just simply write:
#undef OPTIONAL
since it's going to be a
I've applied the patch anyway -- minus the disparaging comment -- since
there's no harm and other people have complained about this. Rev 238.
On Fri, Oct 30, 2009 at 10:56 AM, Oleg Smolsky o...@smolsky.net wrote:
Oh, man you are right. It's a combination of -Werror and -Wextra.
Well, this
Hello,
I have a byte array which I'd like to deserialize, it is about 3K
bytes.
On RHEL 5, 64 bit machine, protobuf 2.2 my deserialization works.
On Leopard 10.5.7 on a macbook it also works. (for both 32 bit and 64
bit versions)
Above gcc: 4.0.1
However, someone reported this crash on
I'm a bit embarrassed :)
The protobuf version of my code uses about 950MB of memory (the Java
Serializable version is only using around 650MB) and I had the java -
Xmx flag set too low; in reality protobuf is extremely fast compared
to Java Serializable:
Java Serializable:
12,000 msgs/sec
