Reviewers: kenton,
Description:
In C++, writing a code generator plugin is as easy as implementing
CodeGenerator and passing an instance to
google::protobuf::compiler::PluginMain; it shouldn't be any harder in
Java (or Python BTW).
This patch adds a JavaHelpers class which is just a port of
Hi,
I have a proto file (first.proto) in folder abc and package abc. I
need to create a new proto file (second.proto) in another folder xyz
and new package, which needs to include first.proto
I have tried
import abc/fist.proto == Doesn't work. Proto Compiler errors
import ../sbc/first.proto ==
When you invoke the proto compiler are you passing a value for -I (the
import path) such that abc/first.proto can be found? It defaults to the
current working directory.
On Wed, Apr 14, 2010 at 9:20 AM, DK deepakkumar.si...@gmail.com wrote:
Hi,
I have a proto file (first.proto) in folder abc
Yes. I had wrong -I flag. Thanks much.
On Wed, Apr 14, 2010 at 11:54 AM, Jason Hsueh jas...@google.com wrote:
When you invoke the proto compiler are you passing a value for -I (the
import path) such that abc/first.proto can be found? It defaults to the
current working directory.
On Wed,
Do I have a typo (or some other misunderstanding) or is there no support for
iterators with RepeatedPtrFields ? Iterators are only available in
RepeatedFields ?
google::protobuf::RepeatedPtrFieldstd::string::iterator it =
message-locations().begin()
Gave me a compilation error that there was no
On Wed, Apr 14, 2010 at 1:15 PM, Andrew Kimpton awkimp...@gmail.com wrote:
Do I have a typo (or some other misunderstanding) or is there no support
for iterators with RepeatedPtrFields ? Iterators are only available in
RepeatedFields ?
google::protobuf::RepeatedPtrFieldstd::string::iterator
On Wed, Apr 14, 2010 at 4:19 PM, Jason Hsueh jas...@google.com wrote:
On Wed, Apr 14, 2010 at 1:15 PM, Andrew Kimpton awkimp...@gmail.comwrote:
Do I have a typo (or some other misunderstanding) or is there no support
for iterators with RepeatedPtrFields ? Iterators are only available in
I understand your explanation, and have changed my automake to;
$(PROTOC) --cpp_out=$(top_srcdir) -I$(top_srcdir) $(PROTOC_FLAGS) $
which seems to handle it.
However, there is still one point we're not connecting on, which is
this. It seems that when a.proto compiles, the name for
