Skip to content

Conversation

@cmcgee1024
Copy link
Member

When building the release binary for swiftly it uses the static linux SDK with musl to create a system independent binary. The SDK was being installed by the build-swiftly-release tool into the user's home directory with "swift sdk install" command and it tries to uninstall it afterwards. This can pollute a user's system or remove the SDK if they installed it already.

In this approach the SDK is extracted into a scratch directory and that directory is provided to the "swift build" command so that it can find it there.

When building the release binary for swiftly it uses the static
linux SDK with musl to create a system independent binary. The
SDK was being installed by the build-swiftly-release tool into
the user's home directory with "swift sdk install" command and
it tries to uninstall it afterwards. This can pollute a user's
system or remove the SDK if they installed it already.

In this approach the SDK is extracted into a scratch directory
and that directory is provided to the "swift build" command so
that it can find it there.
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.

1 participant