There's a hack at the top of message.h to deal with this. I suppose it should have been moved to message_lite.h when lite mode was introduced.
On Thu, Oct 22, 2009 at 2:41 AM, villintehaspam <[email protected]>wrote: > > Hi, > > I am having some troubles with protocol buffers 2.2.0 together with > the windows headers. I receive the following linker error: > > error LNK2019: unresolved external symbol "public: class > google::protobuf::MessageLite const & __thiscall > google::protobuf::internal::ExtensionSet::GetMessageW(int,class > google::protobuf::MessageLite const &)const " (? > getmessa...@extensionset@inter...@protobuf@google@@qbeabvmessagel...@34 > @HABV534@@Z) > > due to the fact that the windows headers define a macro for GetMessage > -> GetMessageW. I was first able to rearrange my includes so that the > windows headers were included after any protobuf-headers, but lately > my rearrangement attempts have been futile and I had to resort to > #undef GetMessage to get things working (which isn't a big issue for > me right now, but it might be later on). > > I noticed that there is an issue note for this (#44) that lists this > as solved in 2.1.0, but that the problem appears to have resurfaced - > is there a current recommended workaround for this other than > rearrange/undef? > > / V > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
