-
Notifications
You must be signed in to change notification settings - Fork 216
Fix up self-discovery of Swift Driver and tools #1067
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
The `arguments` is modified by `Driver.invocationRunMode`, so the first element is no longer the driver itself.
|
Question: Why were we replacing the arguments here? The subsequence is that after replacing |
e150133 to
0b0b451
Compare
This should fix the problem of SwiftPM and other tools not knowing where themselves are.
0b0b451 to
f207c2a
Compare
|
cc @artemcm |
|
Ping |
|
@swift-ci please test |
artemcm
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.
This looks correct to me, thank you.
|
Anyone to merge now? |
|
Ping again for anyone with access to merge:) |
|
@artemcm It seems ready for merge now? |
|
@swift-ci please test |
|
@swift-ci please test Windows platform |
1 similar comment
|
@swift-ci please test Windows platform |
@compnerd does this look familiar? |
|
Yes that seems familiar. swiftlang/llvm-project#5321 should have addressed that. https://ci-external.swift.org/job/oss-swift-windows-toolchain-x86_64-vs2019/ is also green currently. |
|
A subsequent build passed. 👍🏼 |
The
argumentsis modified byDriver.invocationRunMode, so the first element is no longer the driver itself.I’m surprised that no one has discovered this so far👀