I can add pathCommon to my compiler's include path to solve the
problem.  Previously it was only part of the protoc include path

There may be more issues here than I realize, but it's inconvenient
that the generated function uses the filename AND the path, seems like
filename should be sufficient.  If this were the case I could add the
path to the import with ".." and that would also work with the include
statement.

Jason

-- 
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to proto...@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.

Reply via email to