9797f7682b
GENERATED files can be used as dependencies for other targets, so it's misguided (at best) to filter them with a blunt whitelist. However, there does exist an extension that needs to be skipped: on Windows + MSVC, CMake will by default try to generate a Visual Studio project, and there dependencies with no inputs are instead tied to a dummy .rule input file which is created by the generation step. The fileapi will still report those, so it will cause Meson to bail out when it realises there's no such file in the build tree. Fixes #11607 |
||
|---|---|---|
| .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 | ||
| sider.yml | ||
| 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.