-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Forward builtin options to subprojects #14498
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
fdf860d
to
69249c9
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.
The logic looks right to me, but we should be using evolve
here.
3d0658f
to
e437547
Compare
Added a unit test (and verified that it fails without the changes). |
Prepare for adding more complex logic to add_system_option_internal, in order to handle inheritance of global options to subprojects. Do the same in add_project_option to make the similarities and differences evident. Signed-off-by: Paolo Bonzini <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Because system options apply to all subprojects, they need to be present globally whenever a subproject needs them. Signed-off-by: Paolo Bonzini <[email protected]>
The data is already available in the OptionStore's pending_options and add_compiler_option() will pick it from there. Signed-off-by: Paolo Bonzini <[email protected]>
There are several issues here:
Some of these issues were masked by usage of env.options, which should not be needed anymore after the option refactoring; all the required information is stored in OptionStore's pending_options after the
project()
call.Let's see how much this breaks.Fixes: #14497