Re: [Mingw-w64-public] vsnprintf_s found by default though not present in XP, expected?

Exactly for such cases we add emulation-code to our libmingwex.a. To have it within the .def file for msvcrt is for sure nothing we want. Instead we should add an emulation-code for it, as we did already for other such functions. See in our crt the sec_api folder. Regards, Kai 2016-01-09 18:33

Re: [Mingw-w64-public] vsnprintf_s found by default though not present in XP, expected?

On 12/29/15, lh_mouse wrote: > That was because the 'libmsvcrt.a' library was created using a new version > of MSVCRT.DLL which exported the function, but the MSVCRT.DLL shipped with > Windows XP didn't. Yes, I guess the question is (currently the default mechanism can present

Re: [Mingw-w64-public] vsnprintf_s found by default though not present in XP, expected?

That was because the 'libmsvcrt.a' library was created using a new version of MSVCRT.DLL which exported the function, but the MSVCRT.DLL shipped with Windows XP didn't. -- lh_mouse 2015-12-30

[Mingw-w64-public] vsnprintf_s found by default though not present in XP, expected?

As a note, if configure scripts today look for vsnprintf_s they find it "present" however, this causes “the procedure entry point _vsnprintf_s could not be located in the dynamic library msvcrt.dll” on XP boxes. Just calling it out in case this is expected or not, as it somewhat surprised me. $