Skip to content

Fix toolchain stack equality checks when checking if specialized targets are compatible #615

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

Merged
merged 1 commit into from
Jun 26, 2025

Conversation

owenv
Copy link
Collaborator

@owenv owenv commented Jun 26, 2025

When the downloadable Metal toolchain is installed in Xcode, it could cause specialization compatibility checks to fail, causing downstream errors specializing targets representing package plugins. This happened because the compatibility check compared the toolchains of SpecializationParameters with the TOOLCHAINS macro in the configured target's settings. We should use settings.toolchains on the RHS instead to ensure both sides of the comparison have a chance to inject the default toolchain during settings construction.

Closes #614
Closes #570

@owenv
Copy link
Collaborator Author

owenv commented Jun 26, 2025

@swift-ci test

@owenv
Copy link
Collaborator Author

owenv commented Jun 26, 2025

@swift-ci test macOS

@owenv
Copy link
Collaborator Author

owenv commented Jun 26, 2025

@swift-ci test Linux

@owenv
Copy link
Collaborator Author

owenv commented Jun 26, 2025

@swift-ci test macOS

@owenv owenv merged commit f204167 into main Jun 26, 2025
24 checks passed
@owenv owenv deleted the owenv/specialization-toolchain-comparison branch June 26, 2025 22:22
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.

SPM error using latest package from Xcode beta and swift-protobuf Failing to build a package with a swift plugin dependency
2 participants