[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lmi-commits] [lmi] master 94eec13 1/5: Stop imposing the use of C++17 i
From: |
Greg Chicares |
Subject: |
[lmi-commits] [lmi] master 94eec13 1/5: Stop imposing the use of C++17 in configure |
Date: |
Thu, 14 May 2020 17:33:10 -0400 (EDT) |
branch: master
commit 94eec13960db2e06b171354c476b2126abaa9e9c
Author: Vadim Zeitlin <address@hidden>
Commit: Gregory W. Chicares <address@hidden>
Stop imposing the use of C++17 in configure
It's possible (or will soon become possible) to use C++20 too, so don't
override the CXX value specified by the user from configure itself.
Note that this still preserves the check for C++17 support, so if the
compiler doesn't use C++17 or later by default and -std=c++17 or c++20
wasn't specified in CXX, configure will now fail. This is not especially
user-friendly, but more flexible.
---
configure.ac | 2 --
1 file changed, 2 deletions(-)
diff --git a/configure.ac b/configure.ac
index f13b99e..b9835e0 100644
--- a/configure.ac
+++ b/configure.ac
@@ -118,8 +118,6 @@ AC_PROG_CC
CXXFLAGS=${CXXFLAGS:=}
AC_PROG_CXX
-CXX="$CXX -std=c++17"
-
dnl Check if the compiler supports C++17: this is a rather ad hoc test as it
dnl doesn't check for full C++17 support, but it's enough for the subset of it
dnl that is currently used in lmi and this check passes with with g++ 6, which