Chiebot-Mirror/meson - meson - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Christoph Reiter	5a9c9c70df	tests: fix test_meson_installed after the recent appveyor image update Since the last appveyor image update which also included a msys2 update test_meson_installed() fails for the msys2 mingw jobs complaining that the install path isn't included in PYTHONPATH. It complains that "site-packages\" isn't included in "site-packages" ignoring that the separator should be ignored here. Work around the issue by making sure that the path set as PYTHONPATH always ends with os.sep.	6 years ago
Christoph Reiter	eab97e0c44	Workaround python 3.7.1 requiring that PYTHONPATH end in os.sep	6 years ago
Michael Forney	50b2ef7354	Consider 'samu' when looking for ninja command samu prints a different message when the build is a no-op, so make assertBuildIsNoop consider that as well. Also, if compile_commands.json cannot be found, just skip the test. This seems reasonable since meson just produces a warning if `ninja -t compdb` fails. Finally, only capture stdout in run_meson_command_tests.py, since the backend may print messages the tests don't recognize to stderr. Fixes #3405.	6 years ago
Niklas Claesson	4ef4edee2f	tests runners: Refactor out global variables and add argparse	6 years ago
Nirbheek Chauhan	8277d94e24	meson_command_tests: Don't pass pathlib.Path to open [skip appveyor] Closes https://github.com/mesonbuild/meson/issues/4047	6 years ago
Nirbheek Chauhan	c0413f5d49	setup: Add tests for the installed files list Ensure that the installed files list matches what we expect, to avoid surprises at release time.	6 years ago
Nirbheek Chauhan	2ee28029f9	Install meson.exe as the entrypoint on Windows Thanks to Rafael Rivera for the suggestion Fixes https://github.com/mesonbuild/meson/issues/1877	6 years ago
Christoph Burger-Scheidlin	e4a83e47d4	Fix __main__.py for zipapp to work `0a035de` removed main from meson.py breaking the call from __main__.py. This causes zipapps to fail, since the call to meson.main() fails. Copying the invocation from meson.py fixes this issue. Additionally, add a test to run_meson_command_tests.py that builds a zipapp from the source and attempts executing this zipapp with --help to ensure that the resulting zipapp is properly executable.	6 years ago
Nirbheek Chauhan	0a035dea6d	Set the meson command to use when we know what it is Instead of using fragile guessing to figure out how to invoke meson, set the value when meson is run. Also rework how we pass of meson_script_launcher to regenchecker.py -- it wasn't even being used With this change, we only need to guess the meson path when running the tests, and in that case: 1. If MESON_EXE is set in the env, we know how to run meson for project tests. 2. MESON_EXE is not set, which means we run the configure in-process for project tests and need to guess what meson to run, so either - meson.py is found next to run_tests.py, or - meson, meson.py, or meson.exe is in PATH Otherwise, you can invoke meson in the following ways: 1. meson is installed, and mesonbuild is available in PYTHONPATH: - meson, meson.py, meson.exe from PATH - python3 -m mesonbuild.mesonmain - python3 /path/to/meson.py - meson is a shell wrapper to meson.real 2. meson is not installed, and is run from git: - Absolute path to meson.py - Relative path to meson.py - Symlink to meson.py All these are tested in test_meson_commands.py, except meson.exe since that involves building the meson msi and installing it.	7 years ago