Skip to content

Conversation

@artemcm
Copy link
Contributor

@artemcm artemcm commented May 13, 2024

Cherry-pick of #1583

Explanation: As per swiftlang/swift#70932, when swift-driver is installed via a symlink, it is not able to correctly resolve adjacent tool binaries by following their corresponding symlinks. This is a regression from the old, legacy C++ driver. This change fixes this behavior by having the driver resolve its own path if it is a symlink, first.

Risk: Low. Cases where the added code takes effect were previously not working.

Testing: Expected behavior validated manually by implementor and issue originator (on main)

Resolves swiftlang/swift#70932

@artemcm artemcm requested a review from nkcsgexi May 13, 2024 17:56
@artemcm
Copy link
Contributor Author

artemcm commented May 13, 2024

@swift-ci test

@artemcm
Copy link
Contributor Author

artemcm commented May 15, 2024

@swift-ci test Windows platform

@artemcm
Copy link
Contributor Author

artemcm commented May 15, 2024

@swift-ci test macOS platform

@shahmishal
Copy link
Member

@swift-ci test

@adam-fowler
Copy link

Is there a plan to merge this into 6.0?

@gregcotten
Copy link

sorely needed for swiftly compatibility swiftlang/swiftly#122

@artemcm
Copy link
Contributor Author

artemcm commented Jul 30, 2024

@swift-ci test Windows platform

@gregcotten
Copy link

This should really get merged in - I'm surprised there are not more folks chiming in!

@Amzd
Copy link

Amzd commented Aug 13, 2024

This has blocked me from trying out swift 6 for months so yes please merge this.

@artemcm artemcm merged commit ddec397 into swiftlang:release/6.0 Aug 13, 2024
@artemcm artemcm deleted the 60ResolveSymlinksForSubcommand branch August 13, 2024 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants