Skip to content

Conversation

@compnerd
Copy link
Member

Adjust the toolchain build to use the pinned toolchain rather than the built toolchain. This is particularly important with the lack of ABI stability on Windows. We now uniformly build the toolchain with the same runtime. This extricates the SDK from the toolchain build.

Now that we build the toolchain properly against a SxS installable version of the runtime, we can consume the runtime that we built against and inject that into the toolchain image. This avoids the need to rely on trying to maintain ABI compatibility in an ABI unstable environment.

Adjust the toolchain build to use the pinned toolchain rather than the
built toolchain. This is particularly important with the lack of ABI
stability on Windows. We now uniformly build the toolchain with the same
runtime. This extricates the SDK from the toolchain build.

Now that we build the toolchain properly against a SxS installable
version of the runtime, we can consume the runtime that we built
against and inject that into the toolchain image. This avoids the need
to rely on trying to maintain ABI compatibility in an ABI unstable
environment.
@compnerd compnerd marked this pull request as ready for review November 10, 2025 20:08
@compnerd
Copy link
Member Author

Please test with following PRs:
swiftlang/swift-installer-scripts#478

@swift-ci please smoke test

@compnerd
Copy link
Member Author

Please test with following PRs:
swiftlang/swift-installer-scripts#478

@swift-ci please build toolchain Windows platform

@compnerd
Copy link
Member Author

Please test with following PRs:
swiftlang/swift-installer-scripts#478

@swift-ci please build toolchain windows ARM64 platform

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