-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Do not install binary swiftmodule for Darwin #72590
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
Do not install binary swiftmodule for Darwin #72590
Conversation
Also amend the installation code handling macCatalyst to match the one for regular swiftmodules.
@swift-ci please test |
@swift-ci please test WebAssembly |
@swift-ci please build toolchain |
Discussed this with Evan offline -- the long term solution would be to leverage the |
Does it make sense to invert the flag and add an install Swift module flag instead? |
c5ddf9f
to
cd17f74
Compare
This is needed to support Apple internal configurations that would fail consuming such binary swiftmodule (but work as expected when rebuilding from the swiftinterface). Addresses rdar://124390643
cd17f74
to
0cac358
Compare
@swift-ci please test |
@swift-ci please test WebAssembly |
@swift-ci please build toolchain |
@swift-ci Please Test Source Compatibility Release |
@swift-ci please clean test macOS |
The source compatibility suite has the same 9 failures of the main run. |
Verified this has no changes for the Linux toolchain, and only Darwin binary swiftmodules are dropped in the macOS one:
|
This is needed to support Apple internal configurations that would fail
consuming such binary swiftmodule (but work as expected when rebuilding
from the swiftinterface).
Take the chance to cleanup the installation code for stdlib modules -- namely remove duplication and align the macCatalyst logic.
Addresses rdar://124390643