> It seems the debug vs. release versions of MSVC's STL are > not even binary compatible, I hadn't heard of that before so I wrote a test case. Wrote a release dll/lib and was able to compile both debug and release versions of a 'third party' application that would use the dll/lib/h files. Now, this is similar in structure to how I have my own protobufs library set up. Release dll/lib, that is. Though the binaries I compiled were pitifully simple.
But, suppose you have the dll, a lib and the required header files. You have all the things you need. The functions, their location, how they are called. Surely the DLL would worry about itself. It's a separate moster altogether to the source code you're trying to compile, no? The DLL doesn't have to interface to anything. No headers, no nothing. It only worries about itself, right? Just needs to know what in the dll to execute, and that's managed by the lib file, correct? All you should need are the entry/exit points I'd've though. Though my understanding of DLLs is by no means infallible. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~----------~----~----~----~------~----~------~--~---
