Dist doesn't respect meson configuration
- Dominant language
- Python
- Stars
- 6.6k
- Forks
- 1.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 33
Description
I need to create a tarball from a system that doesn't have one dependency. This dependency is behind a meson option which is enabled by default, so what I usually do is turn that off and then the dependency check is skipped.
However, when doing ninja dist, seems meson is generating the tarball with the default options instead of the configured options, making impossible to generate the tarball.
Ideally ninja dist will take into account the configuration.
Contributor guide
Research direction
Start by reproducing the issue with a Meson option disabled because its dependency is unavailable, then run `ninja dist` and compare the generated tarball's configuration with the configured build. Trace the `ninja dist` entry point and the Meson option handling. Done means the tarball is generated using the configured options rather than the defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100