Skip to content

Delete macOS triple hardcode #6569

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

Conversation

aleksproger
Copy link
Contributor

On macOS hostTriple hardcoded as x86_64-apple-macosx which may not reflect the real host triple. As far as I understand the latest Xcode version are shipped with -print-target-info compatible compiler which allows to get rid of this FIXME

Motivation:

Xcode ships with necessary -print-target-info option
Cleanup of small FIXME and misleading hardcoded value

Modifications:

Make a call to swift compiler on macOS to retrieve the triple information

Result:

macOS triple now reflects real value received from swift compiler

@MaxDesiatov
Copy link
Contributor

@swift-ci smoke test

Aleksei added 2 commits May 19, 2023 10:59
On macOS hostTriple hardcoded as `x86_64-apple-macosx` which may not reflect the real host triple.
As far as I understand the latest Xcode version are shipped with `-print-target-info` compatible compiler which allows to get rid of this `FIXME`

`New behaviour`
Host triple received from compiler even on macOS

`Motivation`
Cleanup of small FIXME

`Result`
Host triple for macOS no more a hardcoded value
@aleksproger aleksproger force-pushed the sapitskiy/fix-hardcoded-macos-triple branch from 4368b68 to ccc3c10 Compare May 19, 2023 08:02
@MaxDesiatov
Copy link
Contributor

@swift-ci smoke test

@MaxDesiatov
Copy link
Contributor

@swift-ci test windows

@aleksproger
Copy link
Contributor Author

@MaxDesiatov seems like you may merge it now

@MaxDesiatov MaxDesiatov merged commit c0f529e into swiftlang:main May 19, 2023
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.

3 participants