On Jun 18, 2012, at 22:49 , Justin Muncaster wrote: > I'm currently changing our build system to be cmake based and I'm again > finding myself fighting with the build system to get the .proto to be > automatically generated in a way where they build correctly.
What specific problems are you having? Errors in clean builds? Errors when modifying a .proto and rebuilding? > How do you organize your proto files when you have many in common libraries? > Do all .proto files live in one folder? Should one avoid "import > a/b/c/d/f.proto"? Do you have any recommendations for how one ought one setup > the cmake build system to work with proto files that are organized as they > are above? Any general recommendations? What I've done on my last project was to put all the .proto source code in their own "proto" directory. But this was a cross-language project, so I was accessing them from both C++ and Java, so that seemed to make the most sense to me. I configured the build to generate all C++ files into build/*, and the java files into build/java, then I included/compiled them from there. The Chrome browser organizes its .proto files in a very different way: http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/metrics/proto/ Hope this helps, Evan -- http://evanjones.ca/ -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@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.
