-
Notifications
You must be signed in to change notification settings - Fork 10.6k
[presets] Actually make https://github.com/swiftlang/swift/pull/81284 work #82358
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
[presets] Actually make https://github.com/swiftlang/swift/pull/81284 work #82358
Conversation
|
@swift-ci please smoke test |
|
I'm not sure how I feel about this. If you're overriding a variable, you should override it. If we want to change the behavior of how the flag works in build-script, it should stay in build-script. But then we will also need a separate mechanism for removing and replacing values as well. |
utils/build-presets.ini
Outdated
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 wonder if we should move this to the buildbot_incremental_base preset? The smoketest preset only gets run if someone explicitly asks for a smoke test, but not if they only ask for PR testing.
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.
Alternatively, it might be good to spell out the flags because at this point, I have no idea what the existing flags are, or where they're coming from. These preset files don't make it easy to track down where flags are coming from.
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.
Alternatively, it might be good to spell out the flags because at this point
Sorry, by spell out the flags you mean...?
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 wonder if we should move this to the
buildbot_incremental_basepreset?
I would rather exclude the possibility of some recurrent no-asserts job accidentally picking this up. Ideally, this should affect only the presets that can be used to fulfill our PR status checks. So perhaps a better alternative is to stick it in a pr-testing preset and apply that to the nodes we use for that purpose.
I don’t think special-casing option merging for |
compnerd
left a comment
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.
CMake recommendations are that CMAKE_C_FLAGS, CMAKE_CXX_FLAGS, CMAKE_Swift_FLAGS are off limits for CMakeLists.txt. If we want to allow the user to specify additional flags, that should require a special option e.g. -D Swift_ADDITIONAL_C_FLAGS=-Werror=unused -D Swift_ADDITIONAL_CXX_FLAGS=-Werror-unused -D Swift_ADDITIONAL_Swift_FLAGS="-Xcc -Werror-unused".
|
To be clear, the options should be added via |
7b9ac8d to
2c7ac28
Compare
Thank you! |
|
@etcwilde ping |
2c7ac28 to
e99f3e8
Compare
|
@swift-ci please smoke test |
|
@swift-ci please smoke test macOS |
1 similar comment
|
@swift-ci please smoke test macOS |
--extra-swift-cmake-options=-DCMAKE_CXX_FLAGS=<flags>overwrites the variable rather than appends to it.