The final release of Protobuf 2.5.0 is now available:
http://code.google.com/p/protobuf/downloads/list
Documentation will be updated soon.
CHANGES
2013-02-27 version 2.5.0:
General
* New notion import public that allows a proto file to forward the
content
it imports to its
Comment #2 on issue 454 by johannes...@googlemail.com: Python API parallel
read access is not thread safe when repeated fields are empty
http://code.google.com/p/protobuf/issues/detail?id=454
Any ideas on this? Actually I would have expected that such a bug will make
it into the next
Comment #3 on issue 454 by xiaof...@google.com: Python API parallel read
access is not thread safe when repeated fields are empty
http://code.google.com/p/protobuf/issues/detail?id=454
I have had a look at this problem before. There are several places where
_fields.iteritems() is used. I
Comment #4 on issue 454 by johannes...@googlemail.com: Python API parallel
read access is not thread safe when repeated fields are empty
http://code.google.com/p/protobuf/issues/detail?id=454
But that's a severe violation of the documented behavior if the message
classes in fact aren't
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 465 by bm_...@yahoo.com.au: Error when running pre-compiled
Windows protoc
http://code.google.com/p/protobuf/issues/detail?id=465
What steps will reproduce the problem?
1.Run protoc on Windows without MinGW /
Updates:
Status: Accepted
Owner: xiaof...@google.com
Comment #1 on issue 465 by xiaof...@google.com: Error when running
pre-compiled Windows protoc
http://code.google.com/p/protobuf/issues/detail?id=465
Ah, seems I was not building the binary correctly. I will fix this
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 466 by shish.gi...@scivisum.co.uk: New release breaks python pip
installs
http://code.google.com/p/protobuf/issues/detail?id=466
What steps will reproduce the problem?
1. pip install protobuf
2. watch stdout:
Comment #2 on issue 465 by xiaof...@google.com: Error when running
pre-compiled Windows protoc
http://code.google.com/p/protobuf/issues/detail?id=465
Hi, I just built and uploaded a new binary. Could you check if the problem
is fixed? Thanks.
--
You received this message because this
Updates:
Status: Accepted
Owner: xiaof...@google.com
Comment #1 on issue 466 by xiaof...@google.com: New release breaks python
pip installs
http://code.google.com/p/protobuf/issues/detail?id=466
(No comment was entered for this change.)
--
You received this message because
After unpacking your RAR file to get protobuff.log, I examined that
file. I believe that file is not a single message, but a set of
messages, and each message has a big-endian uint32 stuck in front of it
which is the length of the following message. For example, the first
four bytes are 0x00,
Hi Chris,
Thank you so much.
I knew it was a multiple message file. But I didn't know they used 4 bytes for
the size.
I tested your way with other files and it worked.
Selmi
On Feb 27, 2013, at 21:49, Christopher Head hea...@gmail.com wrote:
After unpacking your RAR file to get
Comment #3 on issue 465 by bm_...@yahoo.com.au: Error when running
pre-compiled Windows protoc
http://code.google.com/p/protobuf/issues/detail?id=465
Looks to work now,
thanks for your work on this issue
--
You received this message because this project is configured to send all
issue
Comment #4 on issue 465 by bm_...@yahoo.com.au: Error when running
pre-compiled Windows protoc
http://code.google.com/p/protobuf/issues/detail?id=465
Issue can be closed
--
You received this message because this project is configured to send all
issue notifications to this address.
You
Updates:
Status: Fixed
Comment #5 on issue 465 by xiaof...@google.com: Error when running
pre-compiled Windows protoc
http://code.google.com/p/protobuf/issues/detail?id=465
(No comment was entered for this change.)
--
You received this message because this project is configured to
Updates:
Status: Fixed
Comment #2 on issue 466 by xiaof...@google.com: New release breaks python
pip installs
http://code.google.com/p/protobuf/issues/detail?id=466
I have uploaded a release package to the PyPI site. pip install should
work now.
--
You received this message
I am having a bizarre linker problem with the simple program I wrote with
protobuf. When I run the make command I see tons of linker errors like the
following:
user.pb.o:(.rodata._ZTIN4misc4UserE[_ZTIN4misc4UserE]+0x10): undefined
reference to `typeinfo for google::protobuf::Message'
On Thu, Feb 28, 2013 at 5:01 AM, Mohammad Husain farhan1...@hotmail.comwrote:
I am having a bizarre linker problem with the simple program I wrote with
protobuf. When I run the make command I see tons of linker errors like the
following:
You don't appear to include the path to protobuf when compiling
user.pb.o -- there's no explicit rule so it'll just $(CXXFLAGS). You
should either add
%.pb.o: %.pb.cc
$(CC) $(CXXFLAGS) $(pkgconfig --cflags protobuf) -o $@ $^
Or add CXXFLAGS = $(pkgconfig --cflags protobuf) at the top, which
18 matches
Mail list logo
