-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fix two small issues with handling of plugin triples #5945
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
@swift-ci please smoke test |
possible to add a test? |
Not sure what is going in the Windows build:
cc @compnerd |
BTW, it looks like SourceKit-LSP itself is not running Windows for its CI, that seems wrong. Either it should be removed from SwiftPM's preset as well or it should be running Windows builds on its own PRs. cc @shahmishal |
@swift-ci please smoke test linux |
@swift-ci please smoke test windows |
2cd9d77
to
befa20a
Compare
@swift-ci please smoke test |
Ah yes, |
- We were not stringently using version-less triples in all comparisons - We were not merging the supported triples of all executable info entries into the final `toolNamesToTriples` which could lead to incorrect errors about unsupported platforms rdar://101096803
befa20a
to
4497e77
Compare
@swift-ci please smoke test |
Until now, we had two almost identical code paths for processing accessible tools and e.g. the command plugin code didn't get the fixes from #5945. This PR consolidates the two and also fixes a bug regarding executable path handling of vended tools.
Until now, we had two almost identical code paths for processing accessible tools and e.g. the command plugin code didn't get the fixes from #5945. This PR consolidates the two and also fixes a bug regarding executable path handling of vended tools.
toolNamesToTriples
which could lead to incorrect errors about unsupported platformsrdar://101096803