mdist: fix dist scripts in subprojects being marked as superproject scripts

This has never worked for built/found programs, only for script files.

In commit 2fabd4c7dc22373e99fc63823d80083ad30704b8 scripts learned an
attribute stating which subproject they came from. In commit
3990754bf55727ef5593769b48f0a03c6b7a3671 dist scripts learned to run
even from a subproject, and relied on that attribute to know when, in
fact, they came from a subproject.

Unfortunately the original attribute was only set in one half of an
if/else, and the other half returned early with only part of the work
done.

Fixes #9964
1 file changed
tree: 208847840c2ce301cacfe323aa4e1b571f881343
  1. .github/
  2. ci/
  3. cross/
  4. data/
  5. docs/
  6. graphics/
  7. man/
  8. manual tests/
  9. mesonbuild/
  10. packaging/
  11. test cases/
  12. tools/
  13. unittests/
  14. .editorconfig
  15. .flake8
  16. .gitattributes
  17. .gitignore
  18. .lgtm.yml
  19. .mailmap
  20. .mypy.ini
  21. .pylintrc
  22. azure-pipelines.yml
  23. CODEOWNERS
  24. contributing.md
  25. COPYING
  26. MANIFEST.in
  27. meson.py
  28. pyproject.toml
  29. README.md
  30. run_cross_test.py
  31. run_custom_lint.py
  32. run_format_tests.py
  33. run_meson_command_tests.py
  34. run_mypy.py
  35. run_project_tests.py
  36. run_single_test.py
  37. run_tests.py
  38. run_unittests.py
  39. setup.cfg
  40. setup.py
  41. sider.yml
  42. skip_ci.py
README.md

Status

PyPI Build Status Codecov Code Quality: Python Total Alerts

Dependencies

  • Python (version 3.7 or newer)
  • Ninja (version 1.8.2 or newer)

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.