-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[Swift Build] Wire up --jobs #9367
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
base: main
Are you sure you want to change the base?
Conversation
|
Closes #9321 |
|
@swift-ci test |
|
@swift-ci 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.
I know it may be benign, but can we add an automated test against the makeBuildSystem that ensure the SWBBuildRequest has the correct value set vain the various buildParmeters.workers value?
Update the PIF builder to take into account of the `--[auto|disable|enable]-index-store` command line option. When set to `auto`, the PIF builder behaviour does the same as the Native build system. Fixes: swiftlang#9325 Issue: rdar://163961900
Update the SwiftPM's SwiftBuild integration to support enabling `address`, `thread` and `undefined` sanitizers while erroring out on the `scudo` and `fuzzer`. Depends on: swiftlang/swift-build#926
Set the `SWIFT_FORCE_STATIC_LINK_STDLIB` build setting in SwiftBuild accordingly to the command line argument and if it's not on Darwin. In addition, set the SWIFT_RESOURCE_DIR setting as that is what the Native build system does. Fixes: swiftlang#9320 Issue: rdar://163948614
… SwiftBuild correctly
|
@swift-ci test |
Test has been added. |
Adopt the new API on SWBBuildRequest
Depends on #9417
Fixes: #9321