options: Validate option values before adding to augments #15062
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Revised version of #15061
Boolean options need to be translated from string "true" to True and so on, otherwise we will get an assertion later when trying to set the value:
This assertion is being hit because the vo-aacenc wrap sets
b_lundef=trueindefault_options:inproject(), which ends up inself.augmentswhen the project is being invoked as a subproject.The fix is to use set_option even for pending subproject options. This will follow this path:
This regressed in 2bafe7d.
First noticed at: https://github.com/mesonbuild/wrapdb/actions/runs/18123699172/job/51573947286?pr=2425