-
Notifications
You must be signed in to change notification settings - Fork 314
Add support for different arguments per workspace #974
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
Add support for different arguments per workspace #974
Conversation
@swift-ci Please test |
a0a3bd0
to
f4a7f57
Compare
I think these should cover most things. It would be good to also include support for SDKs when support for these is added. |
I agree. Once we add that the SDK option to the command line options of |
@swift-ci Please test |
@swift-ci Please test Windows |
capabilityRegistry: capabilityRegistry, | ||
toolchainRegistry: self.toolchainRegistry, | ||
buildSetup: self.options.buildSetup, | ||
buildSetup: workspaceBuildSetup.merging(self.options.buildSetup), |
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.
Is it expected that the main options can override the workspace options? I would have expected it to be the other way around
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.
Oh, interesting. I thought of it as
- Workspace options usually provide some reasonable defaults
- The global options are the bigger hammer with which you can override everything, similar to how
SWIFT_EXEC
orTOOLCHAINS
override any settings in your Xcode project.
But I’m not particularly to the precedence here. @adam-fowler Do you have any opinions?
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 would expect the workspace options to override the global settings.
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.
OK, I’ll flip the precedence order.
cbdc214
to
22ab201
Compare
@swift-ci Please test |
@swift-ci Please test Windows |
1 similar comment
@swift-ci Please test Windows |
Fixes swiftlang#663 rdar://101815704
22ab201
to
33f4612
Compare
@swift-ci Please test |
@swift-ci Please test Windows |
1 similar comment
@swift-ci Please test Windows |
Fixes #663
rdar://101815704
@adam-fowler Do you think these new options on
WorkspaceFolder
would work for you? You should be able to specify them on both theinitialize
and theworkspace/didChangeWorkspaceFolders
request.