f29f3f9f28
Currently deprecation features use the same logic as new features, but that doesn't work correctly. FeatureNew wants to warn about cases where you claim to support >= 0.40, but use a feature from 0.42; deprecation wants to warn when you claim to support >= 0.50, but use a feature that was replaced in 0.45. To make this work we need to invert the version check in the deprecation function, so that if the deprecation is 0.45, and the supported version is >= 0.50, we get a true not a false. |
||
|---|---|---|
| .github | ||
| ci | ||
| cross | ||
| data | ||
| docs | ||
| graphics | ||
| man | ||
| manual tests | ||
| mesonbuild | ||
| msi | ||
| test cases | ||
| tools | ||
| .coveragerc | ||
| .editorconfig | ||
| .flake8 | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .pylintrc | ||
| .travis.yml | ||
| CODEOWNERS | ||
| COPYING | ||
| MANIFEST.in | ||
| README.md | ||
| __main__.py | ||
| azure-pipelines.yml | ||
| contributing.md | ||
| ghwt.py | ||
| lgtm.yml | ||
| meson.py | ||
| mypy.ini | ||
| pyproject.toml | ||
| run_cross_test.py | ||
| run_meson_command_tests.py | ||
| run_project_tests.py | ||
| run_tests.py | ||
| run_unittests.py | ||
| setup.cfg | ||
| setup.py | ||
| sider.yml | ||
| skip_ci.py | ||
README.md
Status
Dependencies
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.
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 irc channel for Meson is #mesonbuild over at Freenode.
You can use FreeNode's official webchat to connect to this channel.
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.