[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo
Comment #11 on issue 158 by m.boga...@hydrodesk.com: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 How about 2.4.0a? -- 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 247 in protobuf: Ability to redirect file output to stdout
Comment #5 on issue 247 by compuwarescc: Ability to redirect file output to stdout http://code.google.com/p/protobuf/issues/detail?id=247 After further use, I think it's also (and possible more) important to stream the output of the -o tag (a FileDescriptorProto buffer) to stdout. If this gets implemented I would hope support for the -o flag would be included. -- 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] Extending the compiler and programatically importing options
Hi,
I've my own compiler extension that adds some code over the standard
code generated by cppgenerator.
Now, I want to add a custom option, I know I can do that by adding the
custom option extending with a proto file like extend
google.protobuf.MethodOptions{ optional bool foo=5;}.
If I do it that way any .proto file that uses it will need access to
the file that defines the extension and import it.
I was wondering if there is a way of embedding it somehow in my
compiler so that the file is not needed.
My app is basically a codegenerator based on cppgenerator and
google::protobuf::compiler::CommandLineInterface cli where I register
it and then run cli.Run.
I guess somehow it should be possible to add the custom descriptor to
the generator at runtime without the need of the proto file.
Thanks
Arkaitz
--
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] MSVC 2010 x64 build fails tests
Hi, I'm trying to get a 64 bit build of version 2.4.0a of the libraries and unit tests compiled using MSVC 2010. I have it successfully building and passing the tests for the Win32 platform in both release and debug configurations, however when built for x64 it fails a large number of unit tests, additionally the release build crashes near the end of the tests. Has anybody else experienced this, or successfully built the 64 bit version and have it passing the unit tests? Thanks, Mark -- 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 247 in protobuf: Ability to redirect file output to stdout
Comment #6 on issue 247 by ken...@google.com: Ability to redirect file output to stdout http://code.google.com/p/protobuf/issues/detail?id=247 For -o, you can do: protoc my.proto -o/dev/stdout This just doesn't work with --java_out (or whatever lanugage) because it would interpret /dev/stdout to be a directory and would try to create files inside it, which would fail. -- 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 247 in protobuf: Ability to redirect file output to stdout
Comment #7 on issue 247 by compuwarescc: Ability to redirect file output to stdout http://code.google.com/p/protobuf/issues/detail?id=247 Seems to me that will only work on linux where /dev/stdout is a file pointer to stdout. Do you know of any way to do this on a windows platform? -- 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] undefined reference to `google::protobuf::internal::kEmptyString'
i just uninstalled protobuf 2.3.0, and installed 2.4.0a, cleaned my builds and re-built. All is OK until I try to link a program, then I get; undefined reference to `google::protobuf::internal::kEmptyString' quick fix? -- 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: undefined reference to `google::protobuf::internal::kEmptyString'
never mind. even though i had cleaned all of protobuf 2.3.0 out of /usr/local/**, there were still some 2.3.0 files lurking under /usr/lib and /usr/ include. Once i cleaned those out, all was fine. -- 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 158 in protobuf: Push 2.3.0 maven artifact to repo
Comment #12 on issue 158 by g...@google.com: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 I hadn't seen that the new version was uploaded. I'll try to get that out this week. Sorry for the delay. -- 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] issue with Message class when using with generics
Hi all, im new to generics and protoclbuffers concepts
In my application im using generics in one class, following is the my
sample code
public class GPBFormatT extends Message implements IGPBFormatT {
@Override
public byte[] serialize(T t)
{
return t.toByteArray();
}
@Override
public T deSerialize(byte[] value)
{
T.parseFrom(value);
return null;
}
in my above code im using parseFrom method, but the problem is this
method will exist only in concrete classes(not in message class) i.e
which classes extends the Message class, so im unable to access
parseFrom method with this generics. How can i solve this?
Thanks, R.Ramesh
--
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.
