Comment #2 on issue 674 by weegreen...@gmail.com: protoc: can't control
output directory
https://code.google.com/p/protobuf/issues/detail?id=674
Why not improve the documentation with this ticket?
--
You received this message because this project is configured to send all
issue notificati
Updates:
Status: WorkingAsIntended
Owner: xiaof...@google.com
Comment #1 on issue 674 by xiaof...@google.com: protoc: can't control
output directory
https://code.google.com/p/protobuf/issues/detail?id=674
Here is how it works:
Support you invoke protoc as:
protoc -Ipath1 --cp
Comment #2 on issue 673 by weegreen...@gmail.com: protoc: can't control
output directory
https://code.google.com/p/protobuf/issues/detail?id=673
Please document how it's designed to work.
--
You received this message because this project is configured to send all
issue notifications to thi
Updates:
Status: WorkingAsIntended
Owner: xiaof...@google.com
Comment #1 on issue 673 by xiaof...@google.com: protoc: can't control
output directory
https://code.google.com/p/protobuf/issues/detail?id=673
This is just how protocol compiler is designed to work. For C++ and Pyth
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 674 by weegreen...@gmail.com: protoc: can't control output
directory
https://code.google.com/p/protobuf/issues/detail?id=674
May be related to #693.
What steps will reproduce the problem?
1. unzip project
2
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 673 by weegreen...@gmail.com: protoc: can't control output
directory
https://code.google.com/p/protobuf/issues/detail?id=673
I am working on integrating the protoc compiler to my build system, however
I'm fi
