automatically find meson_version for existing project #11254
LunarLambda
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
What I usually do there is to add By setting the version unrealistically low, you're guaranteed to trigger every possible FeatureNew check, and then you can decide which ones to refactor and which ones to document in meson_version. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Meson, like CMake, allows specifying a version requirement to gracefully error if a user is on an unsupported version. While not explicitly stated so, this is very much a "best practice" feature
However, unless one is very meticulous in reading the documentation when writing build definitions, it's probably pretty hard to find what the minimum required version actually is. My projects hover somewhere between 0.56 and 0.60 because of wrap system features, but that took me a good bit to figure out. (The documentation does list most if not all version-relevant information, but it can be hard to pick out of the rest of the text sometimes)
so, would it be possible to add a command that analyses your meson.build file and figures out the version requirement?
It could be integrated into the meson file rewriter too, and what would be even sweeter, if it also tells the user what features determined the minimum version, in case you find its too high and the feature is something that could be lived without
Beta Was this translation helpful? Give feedback.
All reactions