[CMake] Set CMP0157 to OLD when targeting Android with the Windows toolchain#1009
Merged
grynspan merged 1 commit intoswiftlang:mainfrom Mar 10, 2025
Merged
Conversation
Contributor
|
@compnerd Would you please help review? |
Contributor
|
@swift-ci test |
Member
Author
finagolfin
approved these changes
Mar 10, 2025
|
Not a committer but LGTM |
Contributor
|
Waiting for Saleem to sign off, then we can squash and merge. |
Member
|
No need, he didn't comment on the linked Foundation pull either, and this is a tiny pull that his TBC colleagues @weliveindetail and @Steelskin need and won't break anything. If you're okay with it, @grynspan, please go ahead and merge. |
grynspan
approved these changes
Mar 10, 2025
Contributor
|
Alrighty, it's clear the change should only impact Android, so… merging. |
Member
Author
|
Thanks for moving on with this so quickly |
etcwilde
pushed a commit
to etcwilde/swift-testing
that referenced
this pull request
Mar 30, 2025
…olchain (swiftlang#1009) There is no early swift-driver build for the Windows toolchain. As a result, swift-testing fails to build properly when CMP0157 is set to NEW due to object files not being generated. This sets CMP0157 to OLD when targeting Android with the Windows toolchain until the early swift-driver is available on Windows. This is analog to swiftlang/swift-corelibs-foundation#5180 ### Checklist: - [x] Code and documentation should follow the style of the [Style Guide](https://github.com/apple/swift-testing/blob/main/Documentation/StyleGuide.md). - [x] If public symbols are renamed or modified, DocC references should be updated. (cherry picked from commit a5dfbc2)
shahmishal
added a commit
that referenced
this pull request
Mar 30, 2025
🍒6.1: [CMake] Set CMP0157 to OLD when targeting Android with the Windows toolchain (#1009)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
There is no early swift-driver build for the Windows toolchain. As a result, swift-testing fails to build properly when CMP0157 is set to NEW due to object files not being generated.
This sets CMP0157 to OLD when targeting Android with the Windows toolchain until the early swift-driver is available on Windows. This is analog to swiftlang/swift-corelibs-foundation#5180
Checklist: