43ea11ea49
In the preceding commit we have started to perform compiler checks for
the value of `b_sanitize`, which allows us to detect sanitizers that
aren't supported by the compiler toolchain. But we haven't yet loosened
the option itself to accept arbitrary values, so until now it's still
only possible to pass sanitizer combinations known by Meson, which is
quite restrictive.
Lift that restriction by adapting the `b_sanitize` option to become a
free-form array. Like this, users can pass whatever combination of
comma-separated sanitizers to Meson, which will then figure out whether
that combination is supported via the compiler checks. This lifts a
couple of restrictions and makes the supporting infrastructure way more
future proof.
A couple of notes regarding backwards compatibility:
- All previous values of `b_sanitize` will remain valid as the syntax
for free-form array values and valid combo choices is the same. We
also treat 'none' specially so that we know to convert it into an
empty array.
- Even though the option has been converted into a free-form array,
callers of `get_option('b_sanitize')` continue to get a string as
value. We may eventually want to introduce a kwarg to alter this
behaviour, but for now it is expected to be good enough for most use
cases.
Fixes #8283
Fixes #7761
Fixes #5154
Fixes #1582
Co-authored-by: Dylan Baker <dylan@pnwbakers.com>
Signed-off-by: Patrick Steinhardt <ps@pks.im>
|
||
|---|---|---|
| .github | ||
| ci | ||
| cross | ||
| data | ||
| docs | ||
| graphics | ||
| man | ||
| manual tests | ||
| mesonbuild | ||
| packaging | ||
| test cases | ||
| tools | ||
| unittests | ||
| .editorconfig | ||
| .flake8 | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .mypy.ini | ||
| .pylintrc | ||
| CODEOWNERS | ||
| COPYING | ||
| MANIFEST.in | ||
| README.md | ||
| azure-pipelines.yml | ||
| contributing.md | ||
| meson.py | ||
| pyproject.toml | ||
| run_cross_test.py | ||
| run_format_tests.py | ||
| run_meson_command_tests.py | ||
| run_mypy.py | ||
| run_project_tests.py | ||
| run_single_test.py | ||
| run_tests.py | ||
| run_unittests.py | ||
| setup.cfg | ||
| setup.py | ||
| skip_ci.py | ||
README.md
Status
Dependencies
Latest Meson version supporting previous Python versions:
- Python 3.6: 0.61.5
- Python 3.5: 0.56.2
- Python 3.4: 0.45.1
Installing from source
Meson is available on PyPI, so
it can be installed with pip3 install meson. The exact command to
type to install with pip can vary between systems, be sure to use
the Python 3 version of pip.
If you wish you can install it locally with the standard Python command:
python3 -m pip install meson
For builds using Ninja, Ninja can be downloaded directly from Ninja GitHub release page or via PyPI
python3 -m pip install ninja
More on Installing Meson build can be found at the getting meson page.
Creating a standalone script
Meson can be run as a Python zip app. To generate the executable run the following command:
./packaging/create_zipapp.py --outfile meson.pyz --interpreter '/usr/bin/env python3' <source checkout>
Running
Meson requires that you have a source directory and a build directory
and that these two are different. In your source root must exist a
file called meson.build. To generate the build system run this
command:
meson setup <source directory> <build directory>
Depending on how you obtained Meson the command might also be called
meson.py instead of plain meson. In the rest of this document we
are going to use the latter form.
You can omit either of the two directories, and Meson will substitute the current directory and autodetect what you mean. This allows you to do things like this:
cd <source root>
meson setup builddir
To compile, cd into your build directory and type ninja. To run unit
tests, type ninja test.
More on running Meson build system commands can be found at the
running meson page
or by typing meson --help.
Contributing
We love code contributions. See the contribution page on the website for details.
IRC
The channel to use is #mesonbuild either via Matrix (web
interface) or OFTC IRC.
Further info
More information about the Meson build system can be found at the project's home page.
Meson is a registered trademark of Jussi Pakkanen.