Skip to content

[Explicit Module Builds] Skip over binary and systemLibrary targets when generating explicit target build jobs #2939

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
Sep 22, 2020

Conversation

artemcm
Copy link
Contributor

@artemcm artemcm commented Sep 18, 2020

System modules will consist of a .modulemap somewhere in the filesystem, with the path to that module being either manually-specified on the build command or computed based on the system module type (apt, brew).
Similarly, binary targets will bring in an .xcframework, the contents of which will be exposed via search paths.

In both cases, the dependency scanning action in the driver will be automatically be able to detect such targets' modules.

@artemcm
Copy link
Contributor Author

artemcm commented Sep 18, 2020

@swift-ci please smoke test

Copy link
Member

@DougGregor DougGregor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable to me

@artemcm artemcm changed the title [Explicit Module Builds] Skip over binary and systemLirary targets when generating explicit target build jobs [Explicit Module Builds] Skip over binary and systemLibrary targets when generating explicit target build jobs Sep 18, 2020
@artemcm
Copy link
Contributor Author

artemcm commented Sep 22, 2020

@swift-ci please smoke test

@artemcm artemcm merged commit 4f47bf3 into swiftlang:master Sep 22, 2020
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