[protobuf] Re: protobuf make check failures
Broadening to the mailing list. I don't have any immediate suggestions, but perhaps someone on the list does. If you can trim the output to the test failures, the issue might jump out a little more. It looks like there is some issue with the child process in the plugin unittest, at least; something about a STATUS_ACCESS_VIOLATION. On Wed, Apr 20, 2011 at 6:09 PM, Brad wrote: > As requested in your footer, the following (truncated) results are > reported after running make check, when installing protobuf in the > "Hint on install location" > > My Platform is a Windows 7/Cygwin/Quadcore i7 950 64-bit OS. > > Any suggestions you might have may be helpful as protobuf is a prereq > for installation of LDAWN by Professor Jordan Boyd-Graber, in turn a > prereq for my doctoral research. > > Thank you so much in advance! > Brad > > Terminal output upon make clean (truncated): > > [ RUN ] ParseErrorTest.MethodOptionTypeError > [ OK ] ParseErrorTest.MethodOptionTypeError (0 ms) > [ RUN ] ParseErrorTest.ImportNotQuoted > [ OK ] ParseErrorTest.ImportNotQuoted (0 ms) > [ RUN ] ParseErrorTest.MultiplePackagesInFile > [ OK ] ParseErrorTest.MultiplePackagesInFile (0 ms) > [--] 37 tests from ParseErrorTest (11 ms total) > > [--] 18 tests from ParserValidationErrorTest > [ RUN ] ParserValidationErrorTest.PackageNameError > [ OK ] ParserValidationErrorTest.PackageNameError (0 ms) > [ RUN ] ParserValidationErrorTest.MessageNameError > [ OK ] ParserValidationErrorTest.MessageNameError (0 ms) > [ RUN ] ParserValidationErrorTest.FieldNameError > [ OK ] ParserValidationErrorTest.FieldNameError (0 ms) > [ RUN ] ParserValidationErrorTest.FieldTypeError > [ OK ] ParserValidationErrorTest.FieldTypeError (0 ms) > [ RUN ] ParserValidationErrorTest.FieldNumberError > [ OK ] ParserValidationErrorTest.FieldNumberError (0 ms) > [ RUN ] ParserValidationErrorTest.FieldExtendeeError > [ OK ] ParserValidationErrorTest.FieldExtendeeError (0 ms) > [ RUN ] ParserValidationErrorTest.FieldDefaultValueError > [ OK ] ParserValidationErrorTest.FieldDefaultValueError (0 ms) > [ RUN ] ParserValidationErrorTest.FileOptionNameError > [ OK ] ParserValidationErrorTest.FileOptionNameError (0 ms) > [ RUN ] ParserValidationErrorTest.FileOptionValueError > [ OK ] ParserValidationErrorTest.FileOptionValueError (0 ms) > [ RUN ] ParserValidationErrorTest.FieldOptionNameError > [ OK ] ParserValidationErrorTest.FieldOptionNameError (0 ms) > [ RUN ] ParserValidationErrorTest.FieldOptionValueError > [ OK ] ParserValidationErrorTest.FieldOptionValueError (0 ms) > [ RUN ] ParserValidationErrorTest.ExtensionRangeNumberError > [ OK ] ParserValidationErrorTest.ExtensionRangeNumberError (0 > ms) > [ RUN ] ParserValidationErrorTest.EnumNameError > [ OK ] ParserValidationErrorTest.EnumNameError (0 ms) > [ RUN ] ParserValidationErrorTest.EnumValueNameError > [ OK ] ParserValidationErrorTest.EnumValueNameError (0 ms) > [ RUN ] ParserValidationErrorTest.ServiceNameError > [ OK ] ParserValidationErrorTest.ServiceNameError (0 ms) > [ RUN ] ParserValidationErrorTest.MethodNameError > [ OK ] ParserValidationErrorTest.MethodNameError (0 ms) > [ RUN ] ParserValidationErrorTest.MethodInputTypeError > [ OK ] ParserValidationErrorTest.MethodInputTypeError (0 ms) > [ RUN ] ParserValidationErrorTest.MethodOutputTypeError > [ OK ] ParserValidationErrorTest.MethodOutputTypeError (0 ms) > [--] 18 tests from ParserValidationErrorTest (6 ms total) > > [--] 1 test from ParseDecriptorDebugTest > [ RUN ] ParseDecriptorDebugTest.TestAllDescriptorTypes > [ OK ] ParseDecriptorDebugTest.TestAllDescriptorTypes (10 ms) > [--] 1 test from ParseDecriptorDebugTest (10 ms total) > > [--] 17 tests from SourceInfoTest > [ RUN ] SourceInfoTest.BasicFileDecls > [ OK ] SourceInfoTest.BasicFileDecls (0 ms) > [ RUN ] SourceInfoTest.Messages > [ OK ] SourceInfoTest.Messages (0 ms) > [ RUN ] SourceInfoTest.Fields > [ OK ] SourceInfoTest.Fields (0 ms) > [ RUN ] SourceInfoTest.Extensions > [ OK ] SourceInfoTest.Extensions (0 ms) > [ RUN ] SourceInfoTest.NestedExtensions > [ OK ] SourceInfoTest.NestedExtensions (0 ms) > [ RUN ] SourceInfoTest.ExtensionRanges > [ OK ] SourceInfoTest.ExtensionRanges (0 ms) > [ RUN ] SourceInfoTest.NestedMessages > [ OK ] SourceInfoTest.NestedMessages (0 ms) > [ RUN ] SourceInfoTest.Groups > [ OK ] SourceInfoTest.Groups (0 ms) > [ RUN ] SourceInfoTest.Enums > [ OK ] SourceInfoTest.Enums (0 ms) > [ RUN ] SourceInfoTest.EnumValues > [ OK ] SourceInfoTest.EnumValues (0 ms) > [ RUN ] SourceInfoTest.NestedEnums > [ OK ] SourceInfoTest.NestedEnums (0 ms) > [ RUN ] SourceInfoTest.Serv
Re: [protobuf] CodedInputStream and Windows
I suppose this should read POSIX file descriptors, which Windows supports. I have never used protobuf on Windows personally, but the project is tested on Windows during the release process, and zero_copy_stream_unittest.cc has test cases for using file descriptors. On Wed, Apr 20, 2011 at 5:56 PM, Patrick wrote: > I'm in the process of porting my custom protobuf RPC library to > windows and have run into a snag. > > I'm using the CodedInputStream class to read messages. The > documentation for zero_copy_input_stream.h implies that this is only > compatible with linux: > > "These implementations include Unix file descriptors and C++ > iostreams." > > Am I missing something? It was my assumption that the entire protobuf > library was platform independent (at least the external API's). Maybe > someone could point me to an example of instantiating a > CodedInputStream under Windows/VS enviro? > > Regards, > Patrick > > -- > 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] CodedInputStream and Windows
I'm in the process of porting my custom protobuf RPC library to windows and have run into a snag. I'm using the CodedInputStream class to read messages. The documentation for zero_copy_input_stream.h implies that this is only compatible with linux: "These implementations include Unix file descriptors and C++ iostreams." Am I missing something? It was my assumption that the entire protobuf library was platform independent (at least the external API's). Maybe someone could point me to an example of instantiating a CodedInputStream under Windows/VS enviro? Regards, Patrick -- 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: adding submessages to higher message
I found the method:
AddAllocated(Element*)
which I think will add the Pong* that I have already created/allocated myself.
Any input if there is a better method then this to use would be appreciated.
Thanks.
-Aaron
On Wed, Apr 20, 2011 at 4:25 PM, Aaron Rich wrote:
> New to protoco buffers so sorry if this is a simple/stupid question.
>
> I have a proto:
> message WrapperMessage
> {
> enum Type {
> PING = 1;
> PONG = 2;
> }
>
> message Header{
> required Type type = 1;
> required string source = 2;
> required int64 time = 3;
> }
>
> required TIMIHeader header = 1;
> repeated Ping ping= 2;
> repeated Pong pong= 3;
> extensions 500 to max;
> }
>
> message Pong
> {
> optional int32 count =1;
> optional string message = 2;
> }
>
> message Ping
> {
> optional int32 count =1;
> optional string message = 2;
> }
>
>
> I need the wrapper so that I can send multiple other message types
> over a single udp datastream. I was going to make a message factory to
> generate the Ping and Pong messages:
> Pong* pong = myFactory->createPong("Hello");
>
> How can I add this Pong message now to a wrapper? I want to be able to
> use the factory so I can generate several Pong messages at once to
> pack together in a single WrapperMessage before sending. I only see
> that calling:
> WrapperMessage.add_pong()
>
> will give me a Pong* back. But then I either have to merge that will
> my factory message or pass it to factory to populate.
>
> Any suggestions of better way to do this (or improve my proto design)?
>
> Thanks.
>
> -Aaron
>
--
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] adding submessages to higher message
New to protoco buffers so sorry if this is a simple/stupid question.
I have a proto:
message WrapperMessage
{
enum Type {
PING = 1;
PONG = 2;
}
message Header{
required Type type = 1;
required string source = 2;
required int64 time = 3;
}
required TIMIHeader header = 1;
repeated Ping ping= 2;
repeated Pong pong= 3;
extensions 500 to max;
}
message Pong
{
optional int32 count =1;
optional string message = 2;
}
message Ping
{
optional int32 count =1;
optional string message = 2;
}
I need the wrapper so that I can send multiple other message types
over a single udp datastream. I was going to make a message factory to
generate the Ping and Pong messages:
Pong* pong = myFactory->createPong("Hello");
How can I add this Pong message now to a wrapper? I want to be able to
use the factory so I can generate several Pong messages at once to
pack together in a single WrapperMessage before sending. I only see
that calling:
WrapperMessage.add_pong()
will give me a Pong* back. But then I either have to merge that will
my factory message or pass it to factory to populate.
Any suggestions of better way to do this (or improve my proto design)?
Thanks.
-Aaron
--
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 270 in protobuf: Precompiled protoc binary for OS X
I have OSX 10.6 and built with Xcode 3 and 4 with no problems. Did you readme.txt? -- 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] Error in java Main
Good evening, I have been stepping through the non maven compile of proto buffers for Java and everything seems to have compiled correctly. However when I bring the main code into Eclipse as a project I get the following error. The method getUnknownFields() of type GeneratedMessage.Builder must override a superclass method has anyone seen this before or know how I can resolve it? Any help you are able to give will be very much appreciated. -- 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 270 in protobuf: Precompiled protoc binary for OS X
Comment #4 on issue 270 by inder123: Precompiled protoc binary for OS X http://code.google.com/p/protobuf/issues/detail?id=270 I have XCode installed on my MacBook Pro (intel chip, fairly recent) with Leopard. However, make fails on me. Please consider providing precompiled Mac OS X binaries. dhcp-172-19-58-98:protobuf-2.4.0a inder$ make make all-recursive Making all in . Making all in src /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I..-D_THREAD_SAFE -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -O2 -g -DNDEBUG -MT descriptor.lo -MD -MP -MF .deps/descriptor.Tpo -c -o descriptor.lo `test -f 'google/protobuf/descriptor.cc' || echo './'`google/protobuf/descriptor.cc libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -D_THREAD_SAFE -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -O2 -g -DNDEBUG -MT descriptor.lo -MD -MP -MF .deps/descriptor.Tpo -c google/protobuf/descriptor.cc -o descriptor.o google/protobuf/descriptor.cc: In member function ‘virtual const google::protobuf::FieldDescriptor* google::protobuf::DescriptorBuilder::OptionInterpreter::AggregateOptionFinder::FindExtension(google::protobuf::Message*, const std::string&) const’: ./google/protobuf/descriptor.h:1152: error: ‘google::protobuf::internal::Mutex* google::protobuf::DescriptorPool::mutex_’ is private google/protobuf/descriptor.cc:4341: error: within this context ./google/protobuf/descriptor.h:1152: error: ‘google::protobuf::internal::Mutex* google::protobuf::DescriptorPool::mutex_’ is private google/protobuf/descriptor.cc:4342: error: within this context make[2]: *** [descriptor.lo] Error 1 -- 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.
