[CMake] Don't set Python_ADDITIONAL_VERSIONS
authorJonas Devlieghere <jonas@devlieghere.com>
Thu, 18 Jul 2019 15:17:42 +0000 (15:17 +0000)
committerJonas Devlieghere <jonas@devlieghere.com>
Thu, 18 Jul 2019 15:17:42 +0000 (15:17 +0000)
commita5359b1b0754ff70b0a36917a5e61625c951b408
treed3a9727ff3a27ecebc868b1e1ef4fb1f18e51517
parentac958c2ed6ab6f4160194b8d0d9752db73bcb03c
[CMake] Don't set Python_ADDITIONAL_VERSIONS

Until recently, Python_ADDITIONAL_VERSIONS was used to limit LLVM's
Python support to 2.7. Now that both LLVM and LLDB both support Python
3, there's no longer a need to put an arbitrary limit on this.

However, instead of removing the variable, r365692 expanded the list,
which has the (presumably unintentional) side-effect of expression
preference for Python 3.

Instead, as Michal proposed in the original code review, we should just
not set the list at all, and let CMake pick whatever Python interpreter
you have in your path.

This patch removes the Python_ADDITIONAL_VERSIONS variable in llvm,
clang and lld. I've also updated the docs with the default behavior and
how to force a different Python version to be used.

Differential revision: https://reviews.llvm.org/D64894

llvm-svn: 366447
clang/CMakeLists.txt
compiler-rt/CMakeLists.txt
lld/CMakeLists.txt
llvm/CMakeLists.txt
llvm/docs/GettingStarted.rst