Skip to content

[Serialization] Always serialize module-defining .swiftinterface, even if SDK-relative. #70817

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

Conversation

artemcm
Copy link
Contributor

@artemcm artemcm commented Jan 10, 2024

The clients, upon loading, will resolve the SDK-relative path to their SDK location.

Resolves rdar://120673684

@artemcm artemcm force-pushed the SerializeInterfacePathWhenBuildBinaryModule branch from 6d51bed to 1608523 Compare January 10, 2024 18:43
@artemcm artemcm marked this pull request as ready for review January 10, 2024 18:43
@artemcm artemcm requested a review from tshortli as a code owner January 10, 2024 18:43
@artemcm artemcm requested a review from xymus January 10, 2024 18:44
@artemcm artemcm force-pushed the SerializeInterfacePathWhenBuildBinaryModule branch 2 times, most recently from 5d3699f to 5a47a3f Compare January 10, 2024 20:28
@artemcm
Copy link
Contributor Author

artemcm commented Jan 10, 2024

@swift-ci smoke test

@artemcm artemcm enabled auto-merge January 10, 2024 20:29
…ven if SDK-relative.

The clients, upon loading, will resolve the SDK-relative path to their SDK location.

Resolves rdar://120673684
@artemcm artemcm force-pushed the SerializeInterfacePathWhenBuildBinaryModule branch from 5a47a3f to de626ab Compare January 10, 2024 22:06
@artemcm
Copy link
Contributor Author

artemcm commented Jan 10, 2024

@swift-ci smoke test

@artemcm artemcm merged commit f9b64be into swiftlang:main Jan 11, 2024
@artemcm artemcm deleted the SerializeInterfacePathWhenBuildBinaryModule branch January 11, 2024 01:09
artemcm added a commit to artemcm/swift that referenced this pull request Jul 3, 2024
…ing interface for prebuilt binary Swift dependencies

When the dependency scanner picks a pre-built binary module candidate for a given dependency, it needs to be able to attempt to resolve its cross-import overlays relative to the textual interface that the binary module was built from. For example, if a collection of binary modules are located in, and resolved as dependencies from, a pre-built module directory, the scanner must lookup their corresponding cross-import overlays relative to the defining interface as read out from the binary module's MODULE_INTERFACE_PATH. swiftlang#70817 ensures that binary modules serialize the path to their defining textual interface.

Resolves rdar://130778577
artemcm added a commit to artemcm/swift that referenced this pull request Jul 3, 2024
…ing interface for prebuilt binary Swift dependencies

When the dependency scanner picks a pre-built binary module candidate for a given dependency, it needs to be able to attempt to resolve its cross-import overlays relative to the textual interface that the binary module was built from. For example, if a collection of binary modules are located in, and resolved as dependencies from, a pre-built module directory, the scanner must lookup their corresponding cross-import overlays relative to the defining interface as read out from the binary module's MODULE_INTERFACE_PATH. swiftlang#70817 ensures that binary modules serialize the path to their defining textual interface.

Resolves rdar://130778577
artemcm added a commit to artemcm/swift that referenced this pull request Jul 3, 2024
…ing interface for prebuilt binary Swift dependencies

When the dependency scanner picks a pre-built binary module candidate for a given dependency, it needs to be able to attempt to resolve its cross-import overlays relative to the textual interface that the binary module was built from. For example, if a collection of binary modules are located in, and resolved as dependencies from, a pre-built module directory, the scanner must lookup their corresponding cross-import overlays relative to the defining interface as read out from the binary module's MODULE_INTERFACE_PATH. swiftlang#70817 ensures that binary modules serialize the path to their defining textual interface.

Resolves rdar://130778577
artemcm added a commit to artemcm/swift that referenced this pull request Jul 4, 2024
…ing interface for prebuilt binary Swift dependencies

When the dependency scanner picks a pre-built binary module candidate for a given dependency, it needs to be able to attempt to resolve its cross-import overlays relative to the textual interface that the binary module was built from. For example, if a collection of binary modules are located in, and resolved as dependencies from, a pre-built module directory, the scanner must lookup their corresponding cross-import overlays relative to the defining interface as read out from the binary module's MODULE_INTERFACE_PATH. swiftlang#70817 ensures that binary modules serialize the path to their defining textual interface.

Resolves rdar://130778577
artemcm added a commit to artemcm/swift that referenced this pull request Jul 8, 2024
…ing interface for prebuilt binary Swift dependencies

When the dependency scanner picks a pre-built binary module candidate for a given dependency, it needs to be able to attempt to resolve its cross-import overlays relative to the textual interface that the binary module was built from. For example, if a collection of binary modules are located in, and resolved as dependencies from, a pre-built module directory, the scanner must lookup their corresponding cross-import overlays relative to the defining interface as read out from the binary module's MODULE_INTERFACE_PATH. swiftlang#70817 ensures that binary modules serialize the path to their defining textual interface.

Resolves rdar://130778577
artemcm added a commit to artemcm/swift that referenced this pull request Jul 8, 2024
…ing interface for prebuilt binary Swift dependencies

When the dependency scanner picks a pre-built binary module candidate for a given dependency, it needs to be able to attempt to resolve its cross-import overlays relative to the textual interface that the binary module was built from. For example, if a collection of binary modules are located in, and resolved as dependencies from, a pre-built module directory, the scanner must lookup their corresponding cross-import overlays relative to the defining interface as read out from the binary module's MODULE_INTERFACE_PATH. swiftlang#70817 ensures that binary modules serialize the path to their defining textual interface.

Resolves rdar://130778577
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.

2 participants