From b4b7e92cbf5a212cc1c648af86df2dee364d48c8 Mon Sep 17 00:00:00 2001 From: Stephan Bergmann Date: Fri, 8 Jan 2021 10:03:15 +0100 Subject: [PATCH] Use MSVC's /permissive- to make it more standards conforming states: "Starting in Visual Studio 2019 version 16.8, the /std:c++latest option implicitly sets the /permissive- option." We opt-in to /std:c++latest via --with-latest-c++, which I'm using for my local Windows builds, so I already happened to fix all the /permissivie- issues across our code base when I upgraded to MSVC 16.8 (at first being unaware why those issues started to show up for me, then understanding that it was due to my use of --with-latest-c++ and this MSVC 16.8 change). Change-Id: I29779ad7d3c2bb0f3615e16e377a8ea220d9e5f2 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/108961 Tested-by: Jenkins Reviewed-by: Stephan Bergmann --- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 79d9a40c54ed..e845f60a26dd 100644 --- a/configure.ac +++ b/configure.ac @@ -7032,7 +7032,7 @@ if test "$COM" = MSC -a "$COM_IS_CLANG" != TRUE; then else CXXFLAGS_CXX11=-std:c++17 fi - CXXFLAGS_CXX11="$CXXFLAGS_CXX11 -Zc:__cplusplus" + CXXFLAGS_CXX11="$CXXFLAGS_CXX11 -permissive- -Zc:__cplusplus" elif test "$GCC" = "yes" -o "$COM_IS_CLANG" = TRUE; then my_flags='-std=c++17 -std=c++1z' if test "$with_latest_c__" = yes; then