Skip to content

build: repair the sub-build for libdispatch on Windows i686 #39101

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
Aug 31, 2021

Conversation

compnerd
Copy link
Member

When building on Windows i686 with a toolchain build for Windows x64, we
would try to build libdispatch for i686 as x86_64. This obviously would
be incorrect. Explicitly pass the target triple for the sub-builds. We
can do this unconditionally since we always use clang-cl builds. This
allows us to build the SDK only components for Windows i686 from a 64bit
build.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

When building on Windows i686 with a toolchain build for Windows x64, we
would try to build libdispatch for i686 as x86_64.  This obviously would
be incorrect.  Explicitly pass the target triple for the sub-builds.  We
can do this unconditionally since we always use `clang-cl` builds.  This
allows us to build the SDK only components for Windows i686 from a 64bit
build.
@compnerd
Copy link
Member Author

CC: @drexin @gottesmm

@compnerd
Copy link
Member Author

@swift-ci please test

@compnerd
Copy link
Member Author

Excellent suggestion from @gottesmm: this is ripe for conversion to a toolchain file. Doing so should really simplify the amount of logic here. That however is a target for another day. This currently should hopefully allow reviving the 32-bit builds of the Windows SDK.

@compnerd compnerd merged commit a7e999e into swiftlang:main Aug 31, 2021
@compnerd compnerd deleted the targets branch August 31, 2021 15:19
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