Skip to content

build: use the same pattern for detecting Darwin platforms #32182

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
Jun 4, 2020

Conversation

compnerd
Copy link
Member

@compnerd compnerd commented Jun 4, 2020

The host platform should be using CMAKE_SYSTEM_NAME STREQUAL Darwin.
However, we currently drive the host side of the compilation against
custom variables. This makes the migration simpler by ensuring that the
entire file uses the same pattern.

Since is_darwin_based_sdk is now used only in the standard library
build, sink it to the standard library build.

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

Resolves SR-NNNN.

The host platform should be using `CMAKE_SYSTEM_NAME STREQUAL Darwin`.
However, we currently drive the host side of the compilation against
custom variables.  This makes the migration simpler by ensuring that the
entire file uses the same pattern.

Since `is_darwin_based_sdk` is now used only in the standard library
build, sink it to the standard library build.
@compnerd
Copy link
Member Author

compnerd commented Jun 4, 2020

@swift-ci please test

@compnerd
Copy link
Member Author

compnerd commented Jun 4, 2020

CC: @drexin

Copy link
Contributor

@drexin drexin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@compnerd compnerd merged commit e9548b0 into swiftlang:master Jun 4, 2020
@compnerd compnerd deleted the uniformity branch June 4, 2020 20:45
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.

2 participants