[all-commits] [llvm/llvm-project] 058c5d: Raise the minimum Visual Studio version to VS2019
Simon Pilgrim via All-commits
all-commits at lists.llvm.org
Sat Jan 29 02:57:05 PST 2022
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 058c5dfc78cd1a1a6075bba9799e63f3ec871c0d
https://github.com/llvm/llvm-project/commit/058c5dfc78cd1a1a6075bba9799e63f3ec871c0d
Author: Simon Pilgrim <llvm-dev at redking.me.uk>
Date: 2022-01-29 (Sat, 29 Jan 2022)
Changed paths:
M clang/docs/ClangFormatStyleOptions.rst
M clang/docs/UsersManual.rst
M lldb/docs/resources/build.rst
M lldb/docs/resources/test.rst
M llvm/cmake/modules/CheckCompilerVersion.cmake
M llvm/docs/CMake.rst
M llvm/docs/GettingStarted.rst
M llvm/docs/GettingStartedVS.rst
M llvm/docs/ReleaseNotes.rst
M llvm/include/llvm/Support/Compiler.h
Log Message:
-----------
Raise the minimum Visual Studio version to VS2019
As raised here: https://lists.llvm.org/pipermail/llvm-dev/2021-November/153881.html
Now that VS2022 is on general release, LLVM is expected to build on VS2017, VS2019 and VS2022, which is proving hazardous to maintain due to changes in behaviour including preprocessor and constexpr changes. Plus of the few developers that work with VS, many have already moved to VS2019/22.
This patch proposes to raise the minimum supported version to VS2019 (16.x) - I've made the hard limit 16.0 or later, with the soft limit VS2019 16.7 - older versions of VS2019 are "allowed" (at your own risk) via the LLVM_FORCE_USE_OLD_TOOLCHAIN cmake flag.
Differential Revision: https://reviews.llvm.org/D114639
More information about the All-commits
mailing list