Do you possibly have any code you could make available for this?
On Wednesday, June 20, 2012 1:15:33 PM UTC-4, Justin Muncaster wrote:
>
> Okay, so I got this build tree working. I had to:
>
> (1) Modify FindProtobuf.cmake (the build rule) so that I can specify the
> proto_path
> (2) Modify each
Okay, so I got this build tree working. I had to:
(1) Modify FindProtobuf.cmake (the build rule) so that I can specify the
proto_path
(2) Modify each .proto import to specify the file to import using the full
path from the root, even if the files are parallel to the .proto source.
(3) Add CMAKE_
On Jun 19, 2012, at 13:53 , Justin Muncaster wrote:
> 1>Running C++ protocol buffer compiler on common/bar/bar.proto
> 1>common/foo/foo.proto: File not found.
> 1>bar.proto: Import "common/foo/foo.proto" was not found or had errors.
>
> I can fix the error by hacking FindProtobuf.cmake and passing
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 havi
Hello,
I've been using protocol buffers for a while, and I love the library,
however I find that when using them in large projects I generally have to
fight with the compiler to get protoc to play nicely with my build
system. My projects are organized as follows:
common/foo/foo.h
common/foo/fo
