[protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
Updates: Status: WontFix Comment #5 on issue 270 by liuj...@google.com: Precompiled protoc binary for OS X http://code.google.com/p/protobuf/issues/detail?id=270 The mutex_ error was fixed in 2.4.1. Close this issue, as we will probably not provide a pre-compiled protoc for OSX at least in the near future. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] installation in windows
Please take a look at the vsprojects/readme.txt On Wed, Jun 29, 2011 at 9:50 PM, Enrico Viappiani wrote: > Let me ask a stupid question.. I have to install protobuf 2.4.1 C++, > in windows 7 64 bit. > I've done that in ubuntu, but i don't have seen the installation > instruction for windows around.. > I'll use visual c++ 10 express. > Help me.. I'm feeling really stupid! > > -- > 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 > protobuf+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/protobuf?hl=en. > > -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 267 in protobuf: vs2010 tuple name collisions
Updates: Status: Accepted Comment #2 on issue 267 by liuj...@google.com: vs2010 tuple name collisions http://code.google.com/p/protobuf/issues/detail?id=267 Will update the gtest in the next release. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 289 in protobuf: 64 bit release build unit tests fail in MSVC 2010
Updates: Status: Accepted Comment #1 on issue 289 by liuj...@google.com: 64 bit release build unit tests fail in MSVC 2010 http://code.google.com/p/protobuf/issues/detail?id=289 (No comment was entered for this change.) -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 295 in protobuf: C++ Compilation of 2.4.1 fails GLIBCXX_3.4.11 Not found
Comment #2 on issue 295 by liuj...@google.com: C++ Compilation of 2.4.1 fails GLIBCXX_3.4.11 Not found http://code.google.com/p/protobuf/issues/detail?id=295 Sorry for the late reply. Have you solved this issue? Looks like a problem of incompatible libraries. Did you set some specially load flags? -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 297 in protobuf: EncodeDecodeTest.Encode fails on windows xp 64 with vs2008-sp1 (v2.4.1)
Updates: Status: Accepted Comment #1 on issue 297 by liuj...@google.com: EncodeDecodeTest.Encode fails on windows xp 64 with vs2008-sp1 (v2.4.1) http://code.google.com/p/protobuf/issues/detail?id=297 Looks like the test cannot open the file. What's the root directory in which you run the tests.exe? Is it in a shared file system? e.g. \\some-server\blabla -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 267 in protobuf: vs2010 tuple name collisions
Updates: Owner: liuj...@google.com Comment #3 on issue 267 by liuj...@google.com: vs2010 tuple name collisions http://code.google.com/p/protobuf/issues/detail?id=267 Fixed in r400 -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 289 in protobuf: 64 bit release build unit tests fail in MSVC 2010
Comment #2 on issue 289 by liuj...@google.com: 64 bit release build unit tests fail in MSVC 2010 http://code.google.com/p/protobuf/issues/detail?id=289 Hi Mark, Could you please provide some details about how you build the x64 version, e.g. how you changed compiling options after importing the default vs project files. I cannot reproduce the error locally. Thanks, Pherl -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] How to use protoc --decode option?
Hi, I am trying to convert a protobuf stream in to a readable format. I got following exception. protobuf.txt:2:1: Invalid control characters encountered in text. protobuf.txt:2:2: Expected top-level statement (e.g. "message"). protobuf.txt:2:9: Invalid control characters encountered in text. Steps i tried: 1) Built the protobuf message object and saved the output to a file (protobuf.txt). (tried in java) 2) Used the decode option in command line. The arguments are protoc --proto_path= -- decode= protoc --proto_path=D:\Work\ProtoBuf\workspace2_4_0_a\TesteLVIS\src\com \proto D:\Work\ProtoBuf\workspace2_4_0_a\TesteLVIS\src\com\proto \TestSameName.proto --decode=com.ebay.test.Book D:\Work\ProtoBuf \workspace2_4_0_a\TesteLVIS\src\com\proto\protobuf.txt Please let me know what i am doing wrong here? is it something related to file encoding? If so how do i resolve it? -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 302 in protobuf: Skip(count) fails when count offset >2^32 count type should be off_t, not int
Comment #3 on issue 302 by fac2...@gmail.com: Skip(count) fails when count offset >2^32 count type should be off_t, not int http://code.google.com/p/protobuf/issues/detail?id=302 The issue is not about large messages, but about large files. We use collections of small messages stored in large files (see http://campagnelab.org/software/goby/tutorials/developing-with-goby/). Please reconsider the issue considering that: 1. the current C++ API is in effect incompatible with the Java API, that has always supported skipping 64 bits offsets in large files. 2. the issue is not about supporting large messages. 3. we have provided a patch that solves the problem (see post of June 6 2011). As can be shown in the patch, the issue is limited to changing a few signatures to prevent the compiler from rounding a 64 bit integer to a 32bit one. Thanks. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 302 in protobuf: Skip(count) fails when count offset >2^32 count type should be off_t, not int
Comment #4 on issue 302 by liuj...@google.com: Skip(count) fails when count offset >2^32 count type should be off_t, not int http://code.google.com/p/protobuf/issues/detail?id=302 Well, for the java version, I think you mean the LimitedInputStream. That class has to use long to override its super class java.io.FilterInputStream; If you take a look at the c.g.protobuf.CodedInputStream, it uses int32 for size type. public void skipRawBytes(final int size) throws IOException We cannot simply change the Skip() to accept int64 because: 1> In protobuf, we use "int" to describe buffer size, e.g. the constructor of CodedInputStream, PushLimit(), GetDirectBufferPointer(), etc. We cannot change Skip() to accept int64, while leaving others still expecting int32. Users may be confused by the inconsistent size type. Even if we change Skip() to int64, the rest of code will still assumes the underlying buffer size is within int32, which can cause potential problems. 2> ZeroCopyStream interface uses int32. Changing the interface function signature means we need to update all the implementation classes. We could do a large code refactoring inside google, but we cannot change code outside the company. Changing the interface may break existing opensource protobuf users. I believe there are many clients who implement ZeroCopyStream for their IO layer. For your case, I think there are many workarounds. e.g. ensuring the chunk doesn't exceed int32max, and use ZeroCopyStream to operate on each chunk. Or maybe implement your own ZeroCopyStream, which ports large int operation to protobuf API. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 290 in protobuf: Cannot compile Google Protocol Buffers on z/OS
Comment #3 on issue 290 by simonsto...@gmail.com: Cannot compile Google Protocol Buffers on z/OS http://code.google.com/p/protobuf/issues/detail?id=290 I managed to get this working without editing the source files - I specified -Wc,ASCII as a compiler option. Note that this means any generated GPB code must also be built with -Wc,ASCII. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] How to use protoc --decode option?
The protoc reads the input from STDIN. If you pass the payload file name as parameter, protoc will treat that file as a ".proto" file. You should pipe the payload to protoc instead. On Tue, Jul 5, 2011 at 7:30 PM, Ravi wrote: > Hi, > > I am trying to convert a protobuf stream in to a readable format. I > got following exception. > > protobuf.txt:2:1: Invalid control characters encountered in text. > protobuf.txt:2:2: Expected top-level statement (e.g. "message"). > protobuf.txt:2:9: Invalid control characters encountered in text. > > > Steps i tried: > 1) Built the protobuf message object and saved the output to a file > (protobuf.txt). (tried in java) > 2) Used the decode option in command line. The arguments are > protoc --proto_path= -- > decode= the protobuf payload> > > protoc --proto_path=D:\Work\ProtoBuf\workspace2_4_0_a\TesteLVIS\src\com > \proto D:\Work\ProtoBuf\workspace2_4_0_a\TesteLVIS\src\com\proto > \TestSameName.proto --decode=com.ebay.test.Book D:\Work\ProtoBuf > \workspace2_4_0_a\TesteLVIS\src\com\proto\protobuf.txt > > Please let me know what i am doing wrong here? > is it something related to file encoding? If so how do i resolve it? > > > > > > -- > 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 > protobuf+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/protobuf?hl=en. > > -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: How to use protoc --decode option?
Hi, I tried that also. I pasted the payload directly in the command prompt when it asked. I got following error. "Failed to parse input." Thanks, Ravikumar K On Jul 5, 7:06 pm, Pherl Liu wrote: > The protoc reads the input from STDIN. If you pass the payload file name as > parameter, protoc will treat that file as a ".proto" file. You should pipe > the payload to protoc instead. > > On Tue, Jul 5, 2011 at 7:30 PM, Ravi wrote: > > Hi, > > > I am trying to convert a protobuf stream in to a readable format. I > > got following exception. > > > protobuf.txt:2:1: Invalid control characters encountered in text. > > protobuf.txt:2:2: Expected top-level statement (e.g. "message"). > > protobuf.txt:2:9: Invalid control characters encountered in text. > > > Steps i tried: > > 1) Built the protobuf message object and saved the output to a file > > (protobuf.txt). (tried in java) > > 2) Used the decode option in command line. The arguments are > > protoc --proto_path= -- > > decode= > the protobuf payload> > > > protoc --proto_path=D:\Work\ProtoBuf\workspace2_4_0_a\TesteLVIS\src\com > > \proto D:\Work\ProtoBuf\workspace2_4_0_a\TesteLVIS\src\com\proto > > \TestSameName.proto --decode=com.ebay.test.Book D:\Work\ProtoBuf > > \workspace2_4_0_a\TesteLVIS\src\com\proto\protobuf.txt > > > Please let me know what i am doing wrong here? > > is it something related to file encoding? If so how do i resolve it? > > > -- > > 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 > > protobuf+unsubscr...@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/protobuf?hl=en. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] Re: How to use protoc --decode option?
Can you try: protoc [various options] < payload.txt So that the content will be read as STDIN to protoc. On Tue, Jul 5, 2011 at 10:12 PM, Ravi wrote: > Hi, > > I tried that also. I pasted the payload directly in the command prompt > when it asked. > I got following error. > > "Failed to parse input." > > Thanks, > Ravikumar K > > On Jul 5, 7:06 pm, Pherl Liu wrote: > > The protoc reads the input from STDIN. If you pass the payload file name > as > > parameter, protoc will treat that file as a ".proto" file. You should > pipe > > the payload to protoc instead. > > > > On Tue, Jul 5, 2011 at 7:30 PM, Ravi > wrote: > > > Hi, > > > > > I am trying to convert a protobuf stream in to a readable format. I > > > got following exception. > > > > > protobuf.txt:2:1: Invalid control characters encountered in text. > > > protobuf.txt:2:2: Expected top-level statement (e.g. "message"). > > > protobuf.txt:2:9: Invalid control characters encountered in text. > > > > > Steps i tried: > > > 1) Built the protobuf message object and saved the output to a file > > > (protobuf.txt). (tried in java) > > > 2) Used the decode option in command line. The arguments are > > > protoc --proto_path= -- > > > decode= > > the protobuf payload> > > > > > protoc --proto_path=D:\Work\ProtoBuf\workspace2_4_0_a\TesteLVIS\src\com > > > \proto D:\Work\ProtoBuf\workspace2_4_0_a\TesteLVIS\src\com\proto > > > \TestSameName.proto --decode=com.ebay.test.Book D:\Work\ProtoBuf > > > \workspace2_4_0_a\TesteLVIS\src\com\proto\protobuf.txt > > > > > Please let me know what i am doing wrong here? > > > is it something related to file encoding? If so how do i resolve it? > > > > > -- > > > 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 > > > protobuf+unsubscr...@googlegroups.com. > > > For more options, visit this group at > > >http://groups.google.com/group/protobuf?hl=en. > > -- > 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 > protobuf+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/protobuf?hl=en. > > -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 289 in protobuf: 64 bit release build unit tests fail in MSVC 2010
Comment #3 on issue 289 by m...@bakedbeans.com: 64 bit release build unit tests fail in MSVC 2010 http://code.google.com/p/protobuf/issues/detail?id=289 Hi Pherl, below are the steps I had to go through to get it to build. * Rename gtest directort to gtest.orig * Download gtest 1.6.0 * Extract to replace original gtest directory * Open gtest.sln in VS2010 to convert the projects then close MSVC * Open protobuf.sln in VS2010 * Follow conversion process as usual * Select menu Build->Configuration Manager * Select 'Active solution platform' dropdown and choose * Choose x64 as platform and copy settings from Win32, make sure create new project platforms is selected * Close configuration manager * Make sure that x64 platform is selected * Confirm that all projects are using the same C/C++ runtime library * Build the projects * Run tests.exe -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 311 in protobuf: PyPI packages cannot be installed with PIP
Comment #2 on issue 311 by wins...@netwok.org: PyPI packages cannot be installed with PIP http://code.google.com/p/protobuf/issues/detail?id=311 FYI, the package_dir argument of setup will probably help: http://docs.python.org/distutils/setupscript#listing-whole-packages -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 311 in protobuf: PyPI packages cannot be installed with PIP
Comment #3 on issue 311 by wins...@netwok.org: PyPI packages cannot be installed with PIP http://code.google.com/p/protobuf/issues/detail?id=311 This is a duplicate of issue #66. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 66 in protobuf: cannot install using easy_install
Comment #35 on issue 66 by wins...@netwok.org: cannot install using easy_install http://code.google.com/p/protobuf/issues/detail?id=66 Are you sure you cannot remove a file hosted on PyPI and reupload it? -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 66 in protobuf: cannot install using easy_install
Comment #36 on issue 66 by sorin.sb...@gmail.com: cannot install using easy_install http://code.google.com/p/protobuf/issues/detail?id=66 I you do not know how to properly define setup.py and to deploy a package to PyPI please take a look at https://github.com/ssbarnea/tendo - release.sh and setup.py should be simple enough to explain what you have to do. When you have the new release ready, just run release.sh -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 66 in protobuf: cannot install using easy_install
Comment #37 on issue 66 by timothee.peignier: cannot install using easy_install http://code.google.com/p/protobuf/issues/detail?id=66 You can't replace file on pypi if you're not the original author, unless original author give you permission. Unless you change the package name ... -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 66 in protobuf: cannot install using easy_install
Comment #38 on issue 66 by wins...@netwok.org: cannot install using easy_install http://code.google.com/p/protobuf/issues/detail?id=66 Sorin: your setup script uses setuptools, not distutils, and has at least one bug: it uses py_modules instead of packages. I’d recommend the official documentation, http://docs.python.org/distutils/setupscript Caveat: I’m a distutils developer :) -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 291 in protobuf: PluginMain is not exported in DLL version
Comment #2 on issue 291 by liuj...@google.com: PluginMain is not exported in DLL version http://code.google.com/p/protobuf/issues/detail?id=291 Fixed in r401. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 308 in protobuf: unresolved external symbol kEmptyString when linking protobuf as a dll.
Comment #2 on issue 308 by liuj...@google.com: unresolved external symbol kEmptyString when linking protobuf as a dll. http://code.google.com/p/protobuf/issues/detail?id=308 Fixed in r401. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] c++/CLI and protobuf-net
Hi I'm quite new in .net programming. I couldn't find any examples of using protobuf-net .net classes from c++ code. I have to write client app working with specified using protobuf protocol. And I don't know now If should I wrote it in standard C++ using protobuf or in C++/CLI using protobuf-net. If I thinking correctly I should not mix C++/CLI with standard C++ (by e.g. using protobuf reference implementation). Unfortunately I could not write in c#. I will be grateful for any advice! -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 289 in protobuf: 64 bit release build unit tests fail in MSVC 2010
Comment #4 on issue 289 by liuj...@google.com: 64 bit release build unit tests fail in MSVC 2010 http://code.google.com/p/protobuf/issues/detail?id=289 Strange, I did the same, but all the tests passed... Could you please upload the generated unittest.pb.h and unittest.pb.cc? You can find them in vsprojects\google\protobuf\ directory. From your log, a few default_xxx fields accessors seemed to be problematic. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 289 in protobuf: 64 bit release build unit tests fail in MSVC 2010
Comment #5 on issue 289 by m...@bakedbeans.com: 64 bit release build unit tests fail in MSVC 2010 http://code.google.com/p/protobuf/issues/detail?id=289 I've attached the files as requested. Attachments: unittest.pb.h 439 KB unittest.pb.cc 704 KB -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] c++/CLI and protobuf-net
I am not able to advise on either C++ option. However, if your solution doesn't already use .NET I wouldn't introduce a .NET dependency just for this - just use the c++ version. If your solution already contains some .NET classes and your intention is to add some protobuf, then it perhaps is an option; reflector (insert grumble about license change) may be of use in providing a translation between c++/cli <===> c#. Marc On 5 Jul 2011, at 12:33, jakin wrote: > Hi > I'm quite new in .net programming. I couldn't find any examples of > using protobuf-net .net classes from c++ code. > I have to write client app working with specified using protobuf > protocol. > And I don't know now If should I wrote it in standard C++ using > protobuf or in C++/CLI using protobuf-net. > If I thinking correctly I should not mix C++/CLI with standard C++ (by > e.g. using protobuf reference implementation). > Unfortunately I could not write in c#. > I will be grateful for any advice! > > -- > 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 > protobuf+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/protobuf?hl=en. > -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 289 in protobuf: 64 bit release build unit tests fail in MSVC 2010
Comment #6 on issue 289 by liuj...@google.com: 64 bit release build unit
tests fail in MSVC 2010
http://code.google.com/p/protobuf/issues/detail?id=289
OK, so probably a bug of vc2010 x64 platform... The function in question is:
// in strutil.cc
char *InternalFastHexToBuffer(uint64 value, char* buffer, int num_byte) {
static const char *hexdigits = "0123456789abcdef";
buffer[num_byte] = '\0';
for (int i = num_byte - 1; i >= 0; i--) {
buffer[i] = hexdigits[uint32(value) & 0xf];
value >>= 4;
}
return buffer;
}
More specifically, this line: hexdigits[uint32(value) & 0xf];
In release mode, due to unknown optimization, the ultimate value in the
loop will be replaced by the penultimate value... That said:
0x010 will be 0x1100.
A simple fix is to remove the uint32() copy constructor:
hexdigits[value & 0xf];
I don't know why the copy constructor was there though...
--
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
protobuf+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 289 in protobuf: 64 bit release build unit tests fail in MSVC 2010
Comment #7 on issue 289 by m...@bakedbeans.com: 64 bit release build unit tests fail in MSVC 2010 http://code.google.com/p/protobuf/issues/detail?id=289 I get this in debug mode also. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 289 in protobuf: 64 bit release build unit tests fail in MSVC 2010
Comment #8 on issue 289 by liuj...@google.com: 64 bit release build unit tests fail in MSVC 2010 http://code.google.com/p/protobuf/issues/detail?id=289 VC seemed to cache the protoc generated files even if you switch Debug/Release. That's why I couldn't reproduce the error - the debug build was fine. BTW, the files you uploaded were probably generated in debug mode also, as they were correct. Fixed in r402. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 297 in protobuf: EncodeDecodeTest.Encode fails on windows xp 64 with vs2008-sp1 (v2.4.1)
Comment #2 on issue 297 by austin.bingham: EncodeDecodeTest.Encode fails on windows xp 64 with vs2008-sp1 (v2.4.1) http://code.google.com/p/protobuf/issues/detail?id=297 I'm running the test executable directly from the directory in which the build places it, i.e. from c:\src\protobuf-2.4.1\vsprojects\Release. Same problem exists for Debug. This is all on my local disk. -- 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 protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
