-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[CMake] Formalize whether libdispatch is used/allowed #35939
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
@swift-ci please test |
59fef55
to
ae311db
Compare
@buttaface – I think I've addressed your concerns. Feedback would be appreciated. @swift-ci please test |
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.
Nice work simplifying the logic.
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.
This effectively disables the use of SWIFT_BUILD_SYNTAXPARSERLIB
and SWIFT_BUILD_SOURCEKIT
if SWIFT_ENABLE_DISPATCH
is false. I think that if you want to expose the explicit control over dispatch, please use cmake_dependent_option
to ensure that the user cannot set SWIFT_BUILD_SYNTAXPARSERLIB
or SWIFT_BUILD_SOURCEKIT
while SWIFT_ENABLE_DISPATCH
is a false value.
ae311db
to
81b6aca
Compare
Build failed |
Hey @compnerd – It looks like that CMake feature is too new. From one of the Linux builders:
|
Build failed |
@davezarzycki I suspect you missed the |
Accidentally requiring libdispatch is a repeated cmake regression. Let's avoid this entirely by formalizing whether libdispatch is enabled or not rather than infer it.
81b6aca
to
ceea7b2
Compare
@swift-ci please test Windows platform |
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.
I think that this shouldn't change the default behaviour and still allow control over dispatch and validate inputs, so seems reasonable. Please ensure that it passes the Windows CI as well (though I don't see why it wouldn't).
Accidentally requiring libdispatch is a repeated cmake regression. Let's avoid this entirely by formalizing whether libdispatch is enabled or not rather than infer it.