-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Restore 1.8.x behavior of yielding options #14800
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
b8a0046
to
61ecb87
Compare
This is quite a big change in how However, the semantics of |
This makes it possible to adjust the value of the option with a subproject-specific augment. This was an undocumented change in 1.8 which was (voluntarily) undone in commit eae4efa72 ("options: resolve yielding options at the time they are added", 2025-07-13), but is useful. This reimplementation of yielding options makes it possible to presreve the bugfix while restoring this new feature. Reported-by: Nirbheek Chauhan <nirbheek@centricular.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
fb65525
to
405e6b1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…on is set" This reverts commit 9ad10ee. The "if" in set_option() was removed, because get_key_and_value_object_for now always returns the subproject key and option object; remove the function as well. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Meson 1.8.x makes it possible to adjust the value of a yielding option with a subproject-specific augment. This was an undocumented change which was (voluntarily) undone in commit eae4efa72 ("options: resolve yielding options at the time they are added", 2025-07-13).
Since it is useful, try to preserve it by reimplementing yielding options: store a link to the parent project option, and undo it if
set_option
overrides it.Because UserOption lookup now never checks
yielding
, this avoids the issue from #14774 too.