On Nov 13, 5:12 pm, Ross <[EMAIL PROTECTED]> wrote: > Do not mix static and dynamic > runtimes, debug and release, or runtimes from different VS > versions and everything should be fine.
I just got run over by this problem: I put together two different apps recently that were exhibiting a crash that could only be fixed by switching to the DLL version of protobuf. I can't profess to totally understand why. I thought perhaps the apps were linking with some DLLs that were dynamically linking to the C runtime (i.e., were compiled with the /MD switch) and some that were linking statically (/MT). But it turned out that they *all* were being compiled with /MD (in Visual Studio Express 2005, Release mode) . And both apps always crashed immediately on startup. So for me, it's using a *static* protobuf lib that's problematic. As far as I can tell, the DLL version is working just fine for me. I was only able to use the static version in some little standalone test apps. As soon I tried to incorporate it into any 'real' app that uses a lot of DLLs, it was Crash City. Anyone else seeing this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
