MSVC Portability

Zoltán Sólyom z-ismeretlen at
Fri Apr 5 16:43:45 EDT 2013

I take back what I said previously. Making libpurple work with Visual 
Studio is getting more and more troublesome. Another access violation, 
now in fprintf, when libpurple tries to write a log file. It is the same 
problem, some components use a different runtime, so I would have to 
recompile another bunch of DLLs. First I thought it's only libintl, 
which has the fprintf definitions, but it calls into gettext, and also 
uses libiconv. I tried but can't get them to compile with Visual Studio 
unfortunately, so I have to give up using it. So even if libpurple 
itself compiles and would work, there are many DLLs there which won't. 
(Unless someone compiles most of the accompanying DLLs in the future.)

More information about the Devel mailing list