Open radioactiveman opened 2 months ago
Another question, unrelated to --help
but about the python.bytecompile
behavior: why does it use force=True
here?
https://github.com/mesonbuild/meson/blob/dc1b4be6be321e39d21604ab4287c9ce972be4da/mesonbuild/scripts/pycompile.py#L35-L37
This results in recompiling all output files every time, even if most haven't changed, thus noticeably damaging performance in incremental builds (for example, SciPy has ~900 .py
files, and recompiling them all just wastes several seconds every time).
I think, force=True
should be removed, letting compile_file()
to skip up-to-date files. Or, if using force=True
has any real purpose, it should be optional.
meson setup --help
prints confusing information for the options--unity-size
and--python.bytecompile
. It looks like the supported values are listed here instead of the default value.
It's a quirk of UserIntegerOption
and its technically incorrect data structure, which passes the range for choices in, overloaded as default_value, then processes the result to set self.choices. Probably, this can be fixed.
@MikhailRyazanov then perhaps that should be its own distinct ticket?
perhaps that should be its own distinct ticket?
If it doesn't have an obvious answer (I thought I'm just missing something), then I can definitely create a separate issue.
Describe the bug
meson setup --help
prints confusing information for the options--unity-size
and--python.bytecompile
. It looks like the supported values are listed here instead of the default value.To reproduce
meson setup --help
Expected behavior Only one (the actual) default value should be stated here. The supported values should be printed in the first column.
--optimization
does it like this:System parameters
meson --version
: 1.4.1Additional information