summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChun-wei Fan <fanchunwei@src.gnome.org>2019-12-26 15:56:38 +0800
committerKjell Ahlstedt <kjellahlstedt@gmail.com>2019-12-29 18:12:25 +0100
commitd699e1d2c0e3d8673bd77ed9d7ee27816487ca25 (patch)
tree3b27e81cacff7c5018eb81e8ead980b488201670
parent87a933d053c51d128f0d6b16327b484680e8b57a (diff)
downloadsigc++-d699e1d2c0e3d8673bd77ed9d7ee27816487ca25.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 f08b3e2..7589a33 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'