[protobuf] Detecting end of CodedInputStream

2010-06-25 Thread Louis-Marie
Hi, I'm using a CodedInputStream, based on a FileInputStream in C++ to read a sequence of size delimited messages (as discussed in recent posts, I'm building a new CodedInputStream object for each new message, in order to allow parsing large number of events without reaching the total bytes

Re: [protobuf] Detecting end of CodedInputStream

2010-06-25 Thread Evan Jones
On Jun 25, 2010, at 4:40 , Louis-Marie wrote: My question is then: how can I safely detect end of file? I guess I could do something like calling Next() on the underlying FileInputStream until it returns false (end of file) or a non empty buffer (and then call BackUp() to re-queue this buffer

[protobuf] Compile libprotobuf.a with a cross compiler?

2010-06-25 Thread sh
Hi, is it possible to compile libprotobuf.a with a cross compiler and the rest (protoc for example) with the native compiler? -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To

Re: [protobuf] Compile libprotobuf.a with a cross compiler?

2010-06-25 Thread Kenton Varda
This is covered in README.txt. On Fri, Jun 25, 2010 at 1:46 AM, sh seb...@gmail.com wrote: Hi, is it possible to compile libprotobuf.a with a cross compiler and the rest (protoc for example) with the native compiler? -- You received this message because you are subscribed to the Google

[protobuf] FileDescriptor module error and Python library path

2010-06-25 Thread Kala
Hello everyone! I am a beginner of protocol buffers on python environment and installed recent version on two machines: - Ubuntu 10.04 (my local laptop) - CentOS (school's cluster) As I have root account in my local laptop, I installed this package into user folder with the following

Re: [protobuf] FileDescriptor module error and Python library path

2010-06-25 Thread Kenton Varda
The flags you pass to configure only affect the C++ package -- configure/make don't know anything about the python subdirectory (except to include it in the dist), and setup.py doesn't know anything about the stuff outside that directory. Think of them as completely separate packages. setup.py