Skip to content

[Explicit Module Build] Do not serialize binary .swiftmodule dependencies when building explicit interface dependencies #72499

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
Mar 22, 2024

Conversation

artemcm
Copy link
Contributor

@artemcm artemcm commented Mar 21, 2024

No description provided.

@artemcm artemcm requested a review from xymus March 21, 2024 22:03
@artemcm artemcm requested a review from tshortli as a code owner March 21, 2024 22:03
@artemcm
Copy link
Contributor Author

artemcm commented Mar 21, 2024

@swift-ci test

…cies when building explicit interface dependencies

The build-system (swift-driver) is then responsible for validating all inputs to each module and re-scheduling affected modules.
@artemcm artemcm force-pushed the NoStatOnSDKDepsSerialization branch from 8c6307c to a38071e Compare March 21, 2024 22:48
@artemcm artemcm changed the title [Serialization] Do not stat SDK-relative dependencies when collecting serialization deps [Explicit Module Build] Do not serialize binary .swiftmodule dependencies when building explicit interface dependencies Mar 21, 2024
@artemcm
Copy link
Contributor Author

artemcm commented Mar 21, 2024

@swift-ci test

@artemcm artemcm merged commit 8090fcf into swiftlang:main Mar 22, 2024
@artemcm artemcm deleted the NoStatOnSDKDepsSerialization branch March 25, 2024 21:28
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.

3 participants