Separate out swift-native sub-packages #33
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lhoward
force-pushed
the
native-subpackages
branch
from
9ebe046 to
f094a27
Compare
Separate out the swift-native into distinct subpackages that mirror the target packges. This avoids conflicts when building Swift tools for the host system, by avoiding development-only artefacts being installed in the native sysroot. It should also serve to draw attention to new and/or removed files in future Swift versions so the target recipes can be updated.
lhoward
force-pushed
the
native-subpackages
branch
from
f094a27 to
fcb21ca
Compare
|
I like it!! Thanks! |
xtremekforever
approved these changes
Aug 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Separate out the swift-native into distinct subpackages that mirror the target packges. This avoids conflicts when building Swift tools for the host system, by avoiding development-only artefacts being installed in the native sysroot.
It should also serve to draw attention to new and/or removed files in future Swift versions so the target recipes can be updated.