On Fri, Apr 12, 2013 at 7:59 PM, Leonid G <leonid.ge...@gmail.com> wrote:
I am actually working on a build system and in my case all file names are
> an absolute path, not relative. With absolute path method suggested above
> (without -I) fails with
$ google/protobuf/2.3.0/gcc_4.1.2/64/bin/protoc --cpp_out=/mypath/test
> /mypath/test/importing.proto /mypath/test/imported.proto
> /mypath/test/importing.proto: File does not reside within any path
> specified using --proto_path (or -I). You must specify a --proto_path
> which encompasses this file. Note that the proto_path must be an exact
> prefix of the .proto file names -- protoc is too dumb to figure out when
> two paths (e.g. absolute and relative) are equivalent (it's harder than you
> Looks like in general case I do need to set -I to some value. The only
> remaining thing - understand what the correct value for -I.
In your example, it would be -I /mypath
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/protobuf?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.