Skip to content

another round of option refactoring #14644

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

Draft
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

bonzini
Copy link
Collaborator

@bonzini bonzini commented May 26, 2025

This gets to the point where everything that goes into the OptionStore has OptionKey instead of str (with the exception of configure commands, but that's pretty well isolated and could even be moved out of OptionStore altogether).

bonzini added 2 commits May 26, 2025 10:07
The converter in DEFAULT_OPTIONS makes a mapping from OptionKey to Python values,
so use the correct type.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
@bonzini bonzini force-pushed the more-options branch 3 times, most recently from 44b001b to 2854d0a Compare May 26, 2025 09:21
bonzini added 11 commits May 26, 2025 14:04
Starting with Meson 1.8.0, "meson configure" prints some options as
":foo" instead of "foo".  Print the option as it was passed by the
user.

While at it, make errors more consistent and/or correct (e.g.
"Unknown option" instead of "Unknown options").

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Once unknown options will go through accept_as_pending_option, only system options
that really exist in Meson will be accepted.  Adjust the unit tests.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
They must be there when running re-configuring, because the backend cannot
be changed, but they can be pending on the first invocation.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
There is common logic hiding between project() and "meson configure": the
complication that the comment mentions for the "default_options" case
actually applies to "meson configure", to machine files, to command line
options and to project options.  Reuse the same function in all four cases.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
self.project_options is set already a couple lines above.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
The cmd_line_options dictionary is described as having OptionKey keys, so
make sure that cmd_the keys do have the correct type.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Thanks to several fixes applied between commit d37d649 ("Make all
Meson level options overridable per subproject.", 2025-02-13) and now,
OptionStore never gets a string key.  Tighten the type of OptionDict,
and use it whenever possible.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
These were only needed due to issues with covariance; they are not needed
anymore now that the types in options.py are simpler.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
The key is already correct at this point, no need to look up CFLAGS_MAPPING.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
They all look the same now, yay.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant