807f88739e
When building with vs2019 (not ninja), a path length error will be thrown if the path to a resource file is even remotely deep within the tree. This is largely because the target name includes the string "Windows resource for file 'full path'", which is then expanded twice (once for the .vcxproj itself, and once for IntDir) and added to the full path. When combined with the tiny path limits on Windows, it is easy to exceed path limits. This error is largely avoided by the ninja back-end. Unlike the vs back-end, the ninja back-end does not use target.get_id() as part of the project file path, nor does it use target.get_id() as part of get_target_private_dir(). Example error: error MSB4184: The expression "[MSBuild]::NormalizePath( C:\src\mesonbuild\Misc\FreeRDP-master\client\X11\xfreerdp\xfreerdp, f3f7317@@Windows resource for file 'Misc_FreeRDP-master_client_X11_xfreerdp_xfreerdp_xfreerdp.rc'@cus\, f3f7317@@Windows resource for file 'Misc_FreeRDP-master_client_X11_xfreerdp_xfreerdp_xfreerdp.rc'@cus. vcxproj.CopyComplete)" cannot be evaluated. Path: C:\src\mesonbuild\Misc\FreeRDP-master\client\X11\xfreerdp\xfreerdp\f3f7317 @@Windows resource for file 'Misc_FreeRDP-master_client_X11_xfreerdp_xfreerdp_xfreerdp.rc'@cus\f3f7317 @@Windows resource for file 'Misc_FreeRDP-master_client_X11_xfreerdp_xfreerdp_xfreerdp.rc'@cus. vcxproj.CopyComplete exceeds the OS max path limit. The fully qualified file name must be less than 260 characters. |
||
|---|---|---|
| .github | ||
| ci | ||
| cross | ||
| data | ||
| docs | ||
| graphics | ||
| man | ||
| manual tests | ||
| mesonbuild | ||
| msi | ||
| test cases | ||
| tools | ||
| .coveragerc | ||
| .editorconfig | ||
| .flake8 | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .mypy.ini | ||
| .pylintrc | ||
| .travis.yml | ||
| CODEOWNERS | ||
| COPYING | ||
| MANIFEST.in | ||
| README.md | ||
| __main__.py | ||
| azure-pipelines.yml | ||
| contributing.md | ||
| ghwt.py | ||
| lgtm.yml | ||
| meson.py | ||
| pyproject.toml | ||
| run_cross_test.py | ||
| run_meson_command_tests.py | ||
| run_mypy.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.