2013/1/21 Jacek Caban <[email protected]>: > On 01/21/13 13:39, JonY wrote: >> On 1/21/2013 09:43, Herb Thompson wrote: >>> Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf >>> could not be located in the dynamic link library msvcrt.dll' on Windows >>> XP SP1? >>> >>> A: For C++, MinGW-w64 implements 'vswprintf (wchar_t *__stream, const >>> wchar_t *__format, __builtin_va_list __local_argv)' as a call to >>> '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, >>> do not include '_vswprintf'. A workaround for this is to compile any >>> C++ libraries and applications that use 'vswprintf' (with the preceding >>> signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the >>> wxWidgets library for applications to be deployed on XP SP1, build >>> wxWidgets with the following command line: >>> > mingw32-make -f makefile.gcc CPPFLAGS="-D__USE_MINGW_ANSI_STDIO" >> Done as >> https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. >> >> Thanks. >> >> I've also added a caveat section on the side effects of using >> __USE_MINGW_ANSI_STDIO. > > Well, IMO we should fix bugs instead of documenting them... I may look > at this, but I'm not sure when I will find time for that. > > Jacek
Well, in general I agree. We might should do same hack (for older msvcrt versions) as we do for vscanf (as example). Cheers, Kai ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
