More MSVC2008 Woes

2009-05-08 Thread Peter K.
Hi All, OK, so we've compiled the DLL that contains the protocol buffers pieces, we can register the DLL. Now, when we try to execute anything to do with the DLL, we get a call stack that gets to FindFileByName, looks for myfile.proto and promptly causes an exception. Our previous

Re: Bit fields in protocol buffer

2009-05-08 Thread Peter K.
Hi, I'm not a PB expert, but I don't believe that the basic types support bitfields. One way to do it is to just expand each bitfield into a uint32. Another way might be to just refer to all the bitfields as bytes. We chose the first approach, but YMMV. Ciao, Peter K. On May 8, 2:02 am,

Re: More MSVC2008 Woes

2009-05-08 Thread Peter K.
D'oh. Hold that thought. It looks like the C runtimes were different, I'm just re-doing everything making sure they're the same. Watch this space. Ciao, Peter K. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: 2.1.0 release candidate

2009-05-08 Thread Peter K.
Apart from the gtest issue: [==] 669 tests from 93 test cases ran. (21470 ms total) [ PASSED ] 669 tests. on a Windows 2003 Server build machine using MS Dev Studio 2008. Two minor issues, probably due to the Dev Studio version: 1. MS Dev Studio 2008 converts the project on opening

Re: Bit fields in protocol buffer

2009-05-08 Thread Henner Zeller
On Fri, May 8, 2009 at 5:50 AM, Peter K. koots...@gmail.com wrote: Hi, I'm not a PB expert, but I don't believe that the basic types support bitfields. One way to do it is to just expand each bitfield into a uint32. fixed32 or fixed64 would be probably better. uint32 is encoded in

Re: More MSVC2008 Woes

2009-05-08 Thread Peter K.
OK. That didn't help. Working on generating more information. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com To unsubscribe

Compiling Protocol Buffer (64) using gcc in Sun 9 (libgcc_s.so: wrong ELF class: ELFCLASS32)

2009-05-08 Thread acidfilez
I needed to compile pb in 64, here it goes: My Plataform Using Solaris 9. spark, gcc (3.4.6) I compile using this configure. ./configure --prefix=/somewhere/protobuf LDFLAGS=-L$PWD/src/solaris - L/usr/local/lib/sparcv9 CFLAGS=-mcpu=v9 -m64 CXXFLAGS=-mcpu=v9 - m64 Yes this will tell that

[Fwd: Re: Compiling Protocol Buffer (64) using gcc in Sun 9 (libgcc_s.so: wrong ELF class: ELFCLASS32)]

2009-05-08 Thread Magno Cardona
--~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com To unsubscribe from this group, send email to

Re: 2.1.0 release candidate

2009-05-08 Thread Kenton Varda
On Fri, May 8, 2009 at 7:08 AM, Peter K. koots...@gmail.com wrote: 1. MS Dev Studio 2008 converts the project on opening the solution file. Yep, that's expected -- we distribute MSVC 2005 project files (and gtest's are MSVC 2003). 2. cl : Command line warning D9035 : option 'Wp64' has

Re: More MSVC2008 Woes

2009-05-08 Thread Kenton Varda
What does your protoc command-line look like? Does your project contain multiple .proto files that import each other? If so you need to make sure to pass the same -I (or --proto_path) flag to each one. On Fri, May 8, 2009 at 5:47 AM, Peter K. koots...@gmail.com wrote: Hi All, OK, so we've

Re: Bit fields in protocol buffer

2009-05-08 Thread Kenton Varda
On Fri, May 8, 2009 at 9:03 AM, Henner Zeller h.zel...@acm.org wrote: fixed32 or fixed64 would be probably better. uint32 is encoded in variable length which would make bitfields typically larger than necessary. Depends. If you are only using the first few (low-order) bits, then uint32 is

Re: Bit fields in protocol buffer

2009-05-08 Thread Henner Zeller
On Fri, May 8, 2009 at 2:06 PM, Kenton Varda ken...@google.com wrote: On Fri, May 8, 2009 at 9:03 AM, Henner Zeller h.zel...@acm.org wrote: fixed32 or fixed64 would be probably better. uint32 is encoded in variable length which would make bitfields typically larger than necessary.

Re: More MSVC2008 Woes

2009-05-08 Thread Peter K.
On May 8, 5:04 pm, Kenton Varda ken...@google.com wrote: What does your protoc command-line look like?  Does your project contain multiple .proto files that import each other?  If so you need to make sure to pass the same -I (or --proto_path) flag to each one. It's just a single proto file:

Re: More MSVC2008 Woes

2009-05-08 Thread Kenton Varda
Ah, I think I misinterpreted before. I thought you were saying it looked for myfile.proto and failed to find it, then aborted, but that doesn't seem to be what you were saying. In any case, I'd need a precise stack trace to say more but it sounds like you figured it out. On Fri, May 8, 2009 at

Re: Protocol Buffers RPC Server Implemention based on Mina(2.0-M5) and Protobuf(2.0.3)

2009-05-08 Thread clinton . foster
I updated the protobuf-socket-rpc implementation so it leaves the connection open, and I was able to get a 4 or 5 times improvement in the time it takes to run the test. It also solved the problem of running out of ephemeral ports. It was necessary to add a length prefix to the request/response