luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-04-26 00:56:53 +02:00
Code Issues Packages Projects Releases Wiki Activity

meson: Don't skip snprintf/vsnprintf checks under MinGW

Browse Source 
The comment stated that the test isn't good enough, but it correctly
detects a C99 printf when I build with -D__USE_MINGW_ANSI_STDIO=1
and an incompatible printf without it.

Using mingw-w64 from current MSYS2.

https://bugzilla.gnome.org/show_bug.cgi?id=795569
This commit is contained in:
Christoph Reiter 2018-05-10 16:04:01 +02:00 committed by Christoph Reiter
parent a9164f55f7
commit eceac66e86
1 changed files with 4 additions and 4 deletions

8
meson.build

@ -722,10 +722,10 @@ endif
have_good_vsnprintf = false have_good_vsnprintf = false
have_good_snprintf = false have_good_snprintf = false
if host_system == 'windows' if host_system == 'windows' and cc.get_id() == 'msvc'
# Unfortunately the mingw and Visual Studio 2015+ implementations of C99-style # Unfortunately the Visual Studio 2015+ implementations of C99-style
# snprintf and vsnprintf don't seem to be quite good enough, at least not in # snprintf and vsnprintf don't seem to be quite good enough.
# mingw-runtime-3.14. (Sorry, I don't know exactly what is the problem, # (Sorry, I don't know exactly what is the problem,
# but it is related to floating point formatting and decimal point vs. comma.) # but it is related to floating point formatting and decimal point vs. comma.)
# The simple tests in AC_FUNC_VSNPRINTF_C99 and AC_FUNC_SNPRINTF_C99 aren't # The simple tests in AC_FUNC_VSNPRINTF_C99 and AC_FUNC_SNPRINTF_C99 aren't
# rigorous enough to notice, though. # rigorous enough to notice, though.