Hello, I'm having a problem with protoc on Windows 7, which does not seem to like full path names. Notice the five separate command-line (bash/ cygwin actually) invocations below. The first two work fine. The other three use full path names for either/both proto_path and the .proto file, and they all fail. Is this a bug or am I doing something wrong?
$ protoc --proto_path=src/main/protobuf/ --java_out=src/generated/ protobuf src/main/protobuf/One.proto $ protoc --proto_path=src/main/protobuf/ --java_out=C:/dev/src/ generated/protobuf src/main/protobuf/One.proto $ protoc --proto_path=C:/dev/src/main/protobuf/ --java_out=C:/dev/src/ generated/protobuf src/main/protobuf/One.proto C: warning: directory does not exist. /dev/src/main/protobuf/: warning: directory does not exist. src/main/protobuf/One.proto: File does not reside within any path specified using --proto_path (or -I). You must specify a --proto_path which encompa sses 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. ab solute and relative) are equivalent (it's harder than you think). $ protoc --proto_path=src/main/protobuf/ --java_out=C:/dev/src/ generated/protobuf C:/dev/src/main/protobuf/One.proto C:/dev/src/main/protobuf/One.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 think). $ protoc --proto_path=C:/dev/src/main/protobuf/ --java_out=C:/dev/src/ generated/protobuf C:/dev/src/main/protobuf/One.proto C: warning: directory does not exist. /dev/src/main/protobuf/: warning: directory does not exist. C:/dev/src/main/protobuf/One.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 think). -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
