Ah, I think I misinterpreted before. I thought you were saying it looked for myfile.proto and failed to find it, then aborted, but that doesn't seem to be what you were saying. In any case, I'd need a precise stack trace to say more but it sounds like you figured it out.
On Fri, May 8, 2009 at 6:41 PM, Peter K. <koots...@gmail.com> wrote: > > > On May 8, 5:04 pm, Kenton Varda <ken...@google.com> wrote: > > > What does your protoc command-line look like? Does your project contain > > multiple .proto files that import each other? If so you need to make > sure > > to pass the same -I (or --proto_path) flag to each one. > > It's just a single proto file: host.proto. > > The protoc command line is just > > protoc host.proto --cpp_out=generated > > (where generated is where the autogenerated code lives. > > After much mucking about this afternoon, we seem to have resolved the > issue. It may still have been a run-time library version issue > (buried deep down), but I'll need to come back to it with a fresh mind > on Monday to analyze root cause. > > Thanks helps for the suggestions! > > Ciao, > > Peter K. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
