More MSVC2008 Woes

2009-05-08 Thread Peter K.
Hi All, OK, so we've compiled the DLL that contains the protocol buffers pieces, we can register the DLL. Now, when we try to execute anything to do with the DLL, we get a call stack that gets to FindFileByName, looks for myfile.proto and promptly causes an exception. Our previous

Re: More MSVC2008 Woes

2009-05-08 Thread Peter K.
D'oh. Hold that thought. It looks like the C runtimes were different, I'm just re-doing everything making sure they're the same. Watch this space. Ciao, Peter K. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: More MSVC2008 Woes

2009-05-08 Thread Peter K.
OK. That didn't help. Working on generating more information. --~--~-~--~~~---~--~~ 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

Re: More MSVC2008 Woes

2009-05-08 Thread Kenton Varda
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. On Fri, May 8, 2009 at 5:47 AM, Peter K. koots...@gmail.com wrote: Hi All, OK, so we've

Re: More MSVC2008 Woes

2009-05-08 Thread Peter K.
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:

Re: More MSVC2008 Woes

2009-05-08 Thread Kenton Varda
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