summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChun-wei Fan <fanchunwei@src.gnome.org>2019-12-26 14:50:27 +0800
committerKjell Ahlstedt <kjellahlstedt@gmail.com>2019-12-29 18:11:52 +0100
commit82005b8f65e65d8ea9544cb26a007f8c1c6ca27d (patch)
tree63de83942361cfa9bae73df758c2ebe3a818da95
parent3701a6a315eaa43623c5096ab2333a4bbf205784 (diff)
downloadsigc++-82005b8f65e65d8ea9544cb26a007f8c1c6ca27d.tar.gz
meson.build: Fix 'meson dist' on Windows
Since we are assured that we are using Python 3.x on when we run Meson, we do not really need to look for the 'python3' executable, but we could just use whatever Python interpreter that is used to run Meson. This will fix situations where it is commonly the case where we may have multiple Python 3.x installations on Windows (www.python.org, and those from Cygwin/mingw-w64), so that Meson really uses one and only one Python installation to run everything that is Python-related, which will thus fix '[meson|ninja] dist' on Visual Studio builds.
-rw-r--r--meson.build2
1 files changed, 1 insertions, 1 deletions
diff --git a/meson.build b/meson.build
index a91e12d..f05c8a0 100644
--- a/meson.build
+++ b/meson.build
@@ -39,7 +39,7 @@ project_build_root = meson.current_build_dir()
cpp_compiler = meson.get_compiler('cpp')
is_msvc = cpp_compiler.get_id() == 'msvc'
-python3 = import('python').find_installation('python3')
+python3 = import('python').find_installation()
python_version = python3.language_version()
python_version_req = '>= 3.5'