Comment #5 on issue 476 by jsill...@gmail.com: please document how to use
protobuf with maven
http://code.google.com/p/protobuf/issues/detail?id=476
This comment is meant to back up Sergei's and Paul's points. I've led the
migration from Ant to Maven within my company and this wouldn't
Comment #6 on issue 476 by sergei.s...@gmail.com: please document how to
use protobuf with maven
http://code.google.com/p/protobuf/issues/detail?id=476
Uploading to Maven Central with the current co-ordinates won't be possible,
because the plugin uses naming pattern that is reserved
Comment #11 on issue 370 by ek.k...@gmail.com: static initialization
problem with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
Great! My solution in the original post requires updating protoc compiler
(libprotoc.so*) and re-generating *.pb.cc files in application side
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 476 by thkoch2...@gmail.com: please document how to use protobuf
with maven
http://code.google.com/p/protobuf/issues/detail?id=476
I'm preparing an email to googles closure-compiler project about how
Updates:
Status: Accepted
Owner: xiaof...@google.com
Comment #1 on issue 474 by xiaof...@google.com: fix handling of Atomic64 on
x32 ABIs
http://code.google.com/p/protobuf/issues/detail?id=474
Thanks. I'll help apply this patch to protobuf trunk.
BTW, on what platform
Comment #2 on issue 474 by vap...@chromium.org: fix handling of Atomic64 on
x32 ABIs
http://code.google.com/p/protobuf/issues/detail?id=474
i think this is only broken for x32 targets (which is a 32bit ABI for
x86_64 platforms). the NaCL port is the same thing -- it's x32 on x86_64
Comment #6 on issue 469 by wuy...@gmail.com: how to write/read more than
one piece of message to/from a text file in c++
http://code.google.com/p/protobuf/issues/detail?id=469
As said by https://developers.google.com/protocol-buffers/docs/techniques,
the following code is passed to test
Updates:
Status: Fixed
Comment #3 on issue 474 by xiaof...@google.com: fix handling of Atomic64 on
x32 ABIs
http://code.google.com/p/protobuf/issues/detail?id=474
Fixed in r492.
--
You received this message because this project is configured to send all
issue notifications
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 475 by l...@schouw.me: Build Visual Studio 2010 fails
http://code.google.com/p/protobuf/issues/detail?id=475
I just took protobuf of from SVN and build it in Visual Studio 2010, but it
fails because of a link error. Did
Comment #4 on issue 469 by wuy...@gmail.com: how to write/read more than
one piece of message to/from a text file in c++
http://code.google.com/p/protobuf/issues/detail?id=469
Yes,it is just binary data chunk. When I open the file stored some protobuf
messages, it seems like
Comment #5 on issue 469 by wuy...@gmail.com: how to write/read more than
one piece of message to/from a text file in c++
http://code.google.com/p/protobuf/issues/detail?id=469
Yes,it is just binary data chunk. When I open the file stored some protobuf
messages, it seems like
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 474 by vap...@google.com: fix handling of Atomic64 on x32 ABIs
http://code.google.com/p/protobuf/issues/detail?id=474
the file src/google/protobuf/stubs/atomicops.h has this snippet:
typedef int32 Atomic32
Updates:
Status: Invalid
Owner: xiaof...@google.com
Comment #1 on issue 473 by xiaof...@google.com: protoc.exe v 2.5.0 does not
work on windows
http://code.google.com/p/protobuf/issues/detail?id=473
Looking through the linked thread, the problem does not seem
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 470 by richardg...@gmail.com: autogen fails to build,
GOOGLE_PROTOBUF_MIN_PROTOC_VERSION too high
http://code.google.com/p/protobuf/issues/detail?id=470
What steps will reproduce the problem?
1. sync fresh
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 471 by dim...@gmail.com: automake-1.12 warning archiver
requires 'AM_PROG_AR' in 'configure.ac'
http://code.google.com/p/protobuf/issues/detail?id=471
What steps will reproduce the problem?
1. svn up
2
Comment #6 on issue 128 by richardg...@gmail.com: Can not dlopen a library
using a protobuf message twice
http://code.google.com/p/protobuf/issues/detail?id=128
This assert causes problems even if you do not intend to unload the dynamic
library, as it occurs on dlopen. Is it strictly
Comment #1 on issue 471 by dim...@gmail.com: automake-1.12
warning archiver requires 'AM_PROG_AR' in 'configure.ac'
http://code.google.com/p/protobuf/issues/detail?id=471
$ svn diff
Index: configure.ac
===
--- configure.ac
Comment #9 on issue 370 by richardg...@gmail.com: static initialization
problem with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
This is an issue even if you are not unloading shared libraries. We see
this assert when dlopen loads a shared library containing a protobuf
Updates:
Status: Fixed
Owner: xiaof...@google.com
Comment #1 on issue 470 by xiaof...@google.com: autogen fails to build,
GOOGLE_PROTOBUF_MIN_PROTOC_VERSION too high
http://code.google.com/p/protobuf/issues/detail?id=470
Fixed in r490
--
You received this message because
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 472 by agent8...@gmail.com: C++ Versions of ParseDelimitedFrom
writeDelimitedTo
http://code.google.com/p/protobuf/issues/detail?id=472
I request that the java functions ParseDelimitedFrom writeDelimitedTo
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 473 by Andrei.Pozolotin: protoc.exe v 2.5.0 does not work on
windows
http://code.google.com/p/protobuf/issues/detail?id=473
see
https://github.com/openfeed-project/openfeed-protocol-java/issues/4
--
You
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 467 by giri.gun...@gmail.com: options passing as argument for the
protoc command
http://code.google.com/p/protobuf/issues/detail?id=467
What steps will reproduce the problem?
new ehnancment request
What
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 468 by zf5984...@gmail.com: could not compiled this in the MAC os
http://code.google.com/p/protobuf/issues/detail?id=468
hi, when I was compiling protobuf in my MAC, i found lots of errs.
From the followings
Comment #1 on issue 468 by henner.z...@gmail.com: could not compiled this
in the MAC os
http://code.google.com/p/protobuf/issues/detail?id=468
Uhm, the error messages give it away: you don't have any version of awk
installed; and no compiler.
--
You received this message because
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 469 by wuy...@gmail.com: how to write/read more than one piece of
message to/from a text file in c++
http://code.google.com/p/protobuf/issues/detail?id=469
What steps will reproduce the problem?
1.fullfill
Comment #2 on issue 469 by wuy...@gmail.com: how to write/read more than
one piece of message to/from a text file in c++
http://code.google.com/p/protobuf/issues/detail?id=469
Noting
this,https://developers.google.com/protocol-buffers/docs/cpptutorial?hl=zh-CN
gives a example of read
Updates:
Status: Invalid
Owner: xiaof...@google.com
Comment #3 on issue 469 by xiaof...@google.com: how to write/read more than
one piece of message to/from a text file in c++
http://code.google.com/p/protobuf/issues/detail?id=469
You must delimiter your messages by some
Comment #4 on issue 468 by xiaof...@google.com: could not compiled this in
the MAC os
http://code.google.com/p/protobuf/issues/detail?id=468
What's your OS version and Xcode version? I am afraid that protobuf doesn't
officially support compilers other than gcc. However, if it's easy enough
Comment #5 on issue 468 by zf5984...@gmail.com: could not compiled this in
the MAC os
http://code.google.com/p/protobuf/issues/detail?id=468
OS is 10.8.2 and Xcode 4.6.
in this version, OS is no longer supporting gcc, while only supporting llvm
compiler - -
I think I need to install gcc
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
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:
Downloading
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
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
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
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
Updates:
Status: Fixed
Owner: xiaof...@google.com
Comment #2 on issue 403 by xiaof...@google.com: Java service insertion
point needed, patch attached
http://code.google.com/p/protobuf/issues/detail?id=403
Fixed in r476.
--
You received this message because this project
Updates:
Status: Fixed
Comment #4 on issue 456 by xiaof...@google.com: Patch for
/trunk/src/google/protobuf/io/coded_stream_inl.h
http://code.google.com/p/protobuf/issues/detail?id=456
Fixed in r476.
--
You received this message because this project is configured to send all
issue
Updates:
Status: Fixed
Comment #2 on issue 462 by xiaof...@google.com: r475 is incorrect
http://code.google.com/p/protobuf/issues/detail?id=462
Fixed in r476.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may
Updates:
Status: Fixed
Owner: xiaof...@google.com
Comment #2 on issue 442 by xiaof...@google.com:
google.protobuf.text_format.Merge fails to parse values returned from
google.protobuf.text_format.MessageToString
http://code.google.com/p/protobuf/issues/detail?id=442
Fixed
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 464 by ryan.fog...@gmail.com: Inefficient Java handling of
repeated list of primitive types
http://code.google.com/p/protobuf/issues/detail?id=464
What steps will reproduce the problem?
1. Any handling
Updates:
Status: WontFix
Labels: -Type-Defect Type-Enhancement
Comment #1 on issue 463 by xiaof...@google.com: Add Descriptor parameter to
all Parser interface methods in Java.
http://code.google.com/p/protobuf/issues/detail?id=463
Parser API is part of the lite runtime which
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 463 by dav.co...@gmail.com: Add Descriptor parameter to all
Parser interface methods in Java.
http://code.google.com/p/protobuf/issues/detail?id=463
Currently, the Parser interface doesn't have a proposed
Comment #2 on issue 353 by kku...@countertack.com: For widespread adoption,
site should provide official java jar download
http://code.google.com/p/protobuf/issues/detail?id=353
Use maven as suggested in the README.TXT
I just did this and it worked fine to build my own jar
-rw-rw-r-- 1
Comment #8 on issue 460 by dav.co...@gmail.com: Add isDefault() to Java
Message interface as a fast means to verify whether it is a default instance
http://code.google.com/p/protobuf/issues/detail?id=460
1. getSerializedSize() is an expensive operation; yeah, it memoizes itself,
but after
Comment #9 on issue 460 by dav.co...@gmail.com: Add isDefault() to Java
Message interface as a fast means to verify whether it is a default instance
http://code.google.com/p/protobuf/issues/detail?id=460
One
--
You received this message because this project is configured to send all
issue
Comment #10 on issue 460 by dav.co...@gmail.com: Add isDefault() to Java
Message interface as a fast means to verify whether it is a default instance
http://code.google.com/p/protobuf/issues/detail?id=460
Forgot to mention the case for Builders, too. When you build, you want to
know
Comment #11 on issue 460 by xiaof...@google.com: Add isDefault() to Java
Message interface as a fast means to verify whether it is a default instance
http://code.google.com/p/protobuf/issues/detail?id=460
I agree that an isEmpty() method might be more intuitive than
getSerializedSize
Comment #4 on issue 460 by dav.co...@gmail.com: Add isDefault() to Java
Message interface as a fast means to verify whether it is a default instance
http://code.google.com/p/protobuf/issues/detail?id=460
1. Call it isEmpty instead, fine. However, how would you efficiently check
whether
Comment #5 on issue 460 by xiaof...@google.com: Add isDefault() to Java
Message interface as a fast means to verify whether it is a default instance
http://code.google.com/p/protobuf/issues/detail?id=460
You can check if a message is empty using getSerializedSize() == 0. I
don't see why
Comment #6 on issue 460 by dav.co...@gmail.com: Add isDefault() to Java
Message interface as a fast means to verify whether it is a default instance
http://code.google.com/p/protobuf/issues/detail?id=460
looks like a hack to me. Also, with lazy fields you will either get it
wrong
Comment #7 on issue 460 by xiaof...@google.com: Add isDefault() to Java
Message interface as a fast means to verify whether it is a default instance
http://code.google.com/p/protobuf/issues/detail?id=460
getSerializedSize() will force lazy fields to be unpacked? and even get it
wrong? How
Updates:
Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low
Comment #1 on issue 460 by xiaof...@google.com: Add isDefault() to Java
Message interface as a fast means to verify whether it is a default instance
http://code.google.com/p/protobuf/issues/detail?id=460
Updates:
Status: WorkingAsIntended
Comment #4 on issue 459 by xiaof...@google.com: Wildcard input path for
proto files does not work in 2.5.0rc1
http://code.google.com/p/protobuf/issues/detail?id=459
Protocol compiler is not supposed to expand wildcards. I believe the
problem has
Comment #5 on issue 459 by askl...@gmail.com: Wildcard input path for proto
files does not work in 2.5.0rc1
http://code.google.com/p/protobuf/issues/detail?id=459
Protocol compiler is not supposed to expand wildcards.
If that's the case, then there is a bug. The available Protobuf compiler
Comment #6 on issue 459 by liuj...@google.com: Wildcard input path for
proto files does not work in 2.5.0rc1
http://code.google.com/p/protobuf/issues/detail?id=459
The win32 binary is compiled using MinGW32 (statically linked with MinGW32
lib). I think the MinGW32 lib handles wildcast
Comment #7 on issue 459 by askl...@gmail.com: Wildcard input path for proto
files does not work in 2.5.0rc1
http://code.google.com/p/protobuf/issues/detail?id=459
In that case, the Visual Studio solution included in the protobuf source
code has a bug. You need to add /link setargv.obj
Comment #4 on issue 433 by xiaof...@google.com: ValuesIn was not declared
error in 'make check' under Ubuntu
http://code.google.com/p/protobuf/issues/detail?id=433
We have already updated the version of gtest in our trunk. Please help
check if you still experience the same problem
Comment #2 on issue 459 by askl...@gmail.com: Wildcard input path for proto
files does not work in 2.5.0rc1
http://code.google.com/p/protobuf/issues/detail?id=459
So it appears that this problem has nothing to do with source code, but
compiler versions.
I tried compiling 2.4.0, 2.4.1
Comment #3 on issue 459 by askl...@gmail.com: Wildcard input path for proto
files does not work in 2.5.0rc1
http://code.google.com/p/protobuf/issues/detail?id=459
Alright, finally found the answer after a wild goose chase.
In Unix, path expansion has nothing to do with code, but everything
Comment #8 on issue 263 by hansen.j...@gmail.com: Proto parser for Java
http://code.google.com/p/protobuf/issues/detail?id=263
Any movement on this lately? This Quora question (
http://www.quora.com/Protocol-Buffers/Has-anyone-implemented-a-parser-for-proto-files-in-Java
) suggested
Comment #9 on issue 263 by hbls00...@gmail.com: Proto parser for Java
http://code.google.com/p/protobuf/issues/detail?id=263
Have a look at protobuf-gcless linked above (the whole project not just
that one file). dernashe did some good work there and I helped add a few
patches to bring
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 462 by howard.h...@gmail.com: r475 is incorrect
http://code.google.com/p/protobuf/issues/detail?id=462
r475 did:
Modify /trunk/src/google/protobuf/message.cc diff
...
32 32
Comment #3 on issue 458 by dav.co...@gmail.com: Remove clone() from all
interfaces, it is wrong; make them extend Cloneable, instead.
http://code.google.com/p/protobuf/issues/detail?id=458
Also, this AbstractMessage.Builder snippet:
// The compiler produces an error if this is not declared
Comment #1 on issue 459 by askl...@gmail.com: Wildcard input path for proto
files does not work in 2.5.0rc1
http://code.google.com/p/protobuf/issues/detail?id=459
More information:
2.4.0a appears to work.
2.4.1 does not work.
2.5.0rc1 does not work.
Appears to be broken somewhere between
Comment #2 on issue 458 by dav.co...@gmail.com: Remove clone() from all
interfaces, it is wrong; make them extend Cloneable, instead.
http://code.google.com/p/protobuf/issues/detail?id=458
The MessageLite.Builder already implements Cloneable, so only the removal
of clone() method from all
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 460 by dav.co...@gmail.com: Add isDefault() to Java Message
interface as a fast means to verify whether it is a default instance
http://code.google.com/p/protobuf/issues/detail?id=460
What steps
in
CodedInputStream and CodedOutputStream to avoid redundant copies for direct
ByteBuffer.
http://code.google.com/p/protobuf/issues/detail?id=429
Reopened this issue and changed the title to be more specific. The
interface of messages and builders is already fixed and shouldn't be
changed
Comment #3 on issue 269 by xiaof...@google.com: Would like to have byte or
int8 type for the message definition
http://code.google.com/p/protobuf/issues/detail?id=269
Re kumar.sumit:
How are you going to use the byte field to implement a fixed length string?
If byte can, why can't int32
Comment #3 on issue 447 by mike.naq...@gmail.com: No C++11 move constructors
http://code.google.com/p/protobuf/issues/detail?id=447
I think there are some simple C++11 #ifdefs to address this for GCC/Clang
and VS, so it should be doable. This would be a huge win in performance in
same cases
Comment #2 on issue 269 by kumar.su...@hotmail.com: Would like to have byte
or int8 type for the message definition
http://code.google.com/p/protobuf/issues/detail?id=269
This is something I have been looking for as well. I need it for a
different use-case though, want to support fixed
Comment #11 on issue 60 by chen3f...@gmail.com: Support static values
in .proto files
http://code.google.com/p/protobuf/issues/detail?id=60
Support constant in proto is very useful
const int64 DefaultType = 1000;
optional int64 type = 1 [default=DefaultType];
--
You received this message
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 458 by dav.co...@gmail.com: Remove clone() from all interfaces,
it is wrong; make them extend Cloneable, instead.
http://code.google.com/p/protobuf/issues/detail?id=458
Here is the example:
public class C1T
Status: New
Owner:
Labels: Type-Patch
New issue 456 by hayden.r...@gmail.com: Patch for
/trunk/src/google/protobuf/io/coded_stream_inl.h
http://code.google.com/p/protobuf/issues/detail?id=456
string_as_array() can return NULL, so the result should be checked before
passing
Status: New
Owner:
Labels: Type-Patch
New issue 457 by hayden.r...@gmail.com: Patch for
/trunk/src/google/protobuf/io/coded_stream_inl.h
http://code.google.com/p/protobuf/issues/detail?id=457
string_as_array() can return NULL, so check the result before passing it to
memcpy
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 455 by howard.h...@gmail.com: google/protobuf/message.cc is
missing #include istream
http://code.google.com/p/protobuf/issues/detail?id=455
What steps will reproduce the problem?
Compile using clang and libc
Comment #3 on issue 434 by jtolds: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
any chance we could have this ticket reopened and then closed when the new
Comment #4 on issue 434 by xiaof...@google.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
You can just keep an eye on the discussion group. When the new
Updates:
Cc: f...@google.com
Comment #1 on issue 454 by liuj...@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
Adding Frank to take a look.
--
You received this message because you
Comment #2 on issue 368 by olivier@gmail.com: Compilation failure
generating scaladoc from SBT - fix looks trivial
http://code.google.com/p/protobuf/issues/detail?id=368
Confirmed!
--
You received this message because you are subscribed to the Google Groups Protocol
Buffers group
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 453 by kccon...@gmail.com: protobuf-2.5.0rc1 doesn't build with
libc++
http://code.google.com/p/protobuf/issues/detail?id=453
PLEASE apply my patch which fixes protobuf-2.5.0rc1 build with libc
Comment #8 on issue 370 by ylee...@gmail.com: static initialization problem
with dlopen
http://code.google.com/p/protobuf/issues/detail?id=370
using static library will not have this problem.I did.
reconfigure google buffer with :
configrue --disable-shared
before this step ,modify configure
Comment #2 on issue 433 by walker.z...@gmail.com: ValuesIn was not
declared error in 'make check' under Ubuntu
http://code.google.com/p/protobuf/issues/detail?id=433
I experienced the same problem on Fedora 17.
The version of gtest curerntly included in the protobug-2.4.1.tar.gz
downloand
Comment #2 on issue 452 by arjan.jo...@gmail.com: License for protobuf
http://code.google.com/p/protobuf/issues/detail?id=452
Found it! Thank you for your swift reply.
--
You received this message because you are subscribed to the Google Groups Protocol
Buffers group.
To post to this group
Comment #6 on issue 322 by xiaof...@google.com: Add support for parsing
text files that contain a BOM, or UTF preamble for protoc.exe input
http://code.google.com/p/protobuf/issues/detail?id=322
I would argue that since protobuf doesn't support Unicode it doesn't make
sense
Comment #3 on issue 451 by xiaof...@google.com: Make SingleFieldBuilder
truly extendable.
http://code.google.com/p/protobuf/issues/detail?id=451
So what you need is the sub-builder support for DynamicMessage.Builder,
right? I think this is a nice feature to have. Actually we have a TODO
Comment #7 on issue 449 by ltwar...@gmail.com: Link error while using
clang++ with -stdlib=libc++ flag in OSX
http://code.google.com/p/protobuf/issues/detail?id=449
Link in verbose mode and check what things is Your linker pulling in, maybe
it is some default.
--
You received
Updates:
Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low
Comment #4 on issue 322 by xiaof...@google.com: Add support for parsing
text files that contain a BOM, or UTF preamble for protoc.exe input
http://code.google.com/p/protobuf/issues/detail?id=322
We don't
Comment #5 on issue 449 by ltwar...@gmail.com: Link error while using
clang++ with -stdlib=libc++ flag in OSX
http://code.google.com/p/protobuf/issues/detail?id=449
Im doing this in Linux.
My configure:
./configure --prefix=/usr CC=clang CXX=clang++ CXXFLAGS=-O2
-stdlib=libc++ LIBS=-lc
Comment #1 on issue 451 by xiaof...@google.com: Make SingleFieldBuilder
truly extendable.
http://code.google.com/p/protobuf/issues/detail?id=451
SingleFieldBuilder and almost all other classes in protobuf package are not
supposed to be subclassed by users. For this issue we'd better make
Comment #2 on issue 451 by dmtes...@gmail.com: Make SingleFieldBuilder
truly extendable.
http://code.google.com/p/protobuf/issues/detail?id=451
Well, I've implemented a DynamicMessage and DynamicMessage.Builder like
classes to provide the same functionality plus all sub-builders might have
Comment #2 on issue 444 by mjkl...@gmail.com: ShutdownProtobufLibrary()
have to be called from each binaries, not only once.
http://code.google.com/p/protobuf/issues/detail?id=444
Unfortunately, protobuf not supporting CMake makes difficult to maintain
upgrading it when you use the dll
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 449 by yayj...@gmail.com: Link error while using clang++ with
-stdlib=libc++ flag in OSX
http://code.google.com/p/protobuf/issues/detail?id=449
What steps will reproduce the problem?
1. To avoid the affection
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 448 by wuy...@gmail.com: failed to build x64 in vs2008
http://code.google.com/p/protobuf/issues/detail?id=448
What steps will reproduce the problem?
1.add an x64 config or target like other people say,and select
Comment #2 on issue 447 by jacek.si...@grasshopperasia.com: No C++11 move
constructors
http://code.google.com/p/protobuf/issues/detail?id=447
An option to protoc or the preprocessor could solve backward compatibility
--
You received this message because you are subscribed to the Google
801 - 900 of 2000 matches
Mail list logo
