On Thu, Jan 26, 2012 at 1:02 PM, joel <joel.lafond.lapa...@usherbrooke.ca>wrote:
> > I'm not a expert too ... I can't compile individually because > both file depend on the other. You should set the proto path using --proto_path to be the root directory of your protocol buffer files, and then you don't need to compile them together. But if you're saying that test1.proto depends on test2.proto, and test2.proto depends on test1.proto - well, that's simply a bad idea. I'm not 100% sure that the protocol buffer compiler will even accept that (though it probably will), but it's a terrible idea conceptually. Because there are no forward references and no cycles, you can *always* break up your protocol buffer files so that this doesn't happen! > I think i will merge everything > in 1 proto ... it's gonna be long but > more simple!! > Unless there are only ever going to be two protocol buffers, and their files are small, this is not a great idea. It's going to make your builds progressively longer, it makes maintenance harder, there's no good reason for it. Take the extra time and master this tool - it's extremely powerful and flexible, the small amounts of time you spend now will pay off 10x over your project. > > -- > 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. > > -- /t http://radio.swirly.com - art music radio 24/7 366/1000 -- 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.
