-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[build] Don't infer Clang path when crosscompiling #34664
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
[build] Don't infer Clang path when crosscompiling #34664
Conversation
Addresses rdar://71240426
@swift-ci build toolchain macOS |
@swift-ci please smoke test |
Follow up to #34437 |
@swift-ci please test stdlib with toolchain |
preset=stdlib_S_standalone_minimal_macho_x86_64,build,test |
Build failed |
Build failed |
@swift-ci Please Test Source Compatibility |
@swift-ci please smoke test Linux |
Not sure why it's failing on this change |
Those failures seem to be happening on the "main" job as well and makes me think they are unrelated to this change https://ci.swift.org/job/oss-swift-test-stdlib-with-toolchain/62/ I would need to double check locally just in case |
macOS Toolchain Install command |
Hey @edymtt could you share a bit more context on this? I don't understand what this is supposed to do/what it does. From ~CMakeLists.txt:465 if("${SWIFT_NATIVE_LLVM_TOOLS_PATH}" STREQUAL "")
set(SWIFT_CROSS_COMPILING FALSE)
else()
set(SWIFT_CROSS_COMPILING TRUE)
endif() The |
To the best of my understanding, when we are building Swift for the host architecture, we expect When we are cross compiling, those values are set when invoking CMake and we want to consider them -- as such my patch is basically mimicking what we are already doing at https://github.com/apple/swift/pull/34664/files#diff-af70c8d589bfadd011360af736827b9f3e3bd1655f7ceb9f08db8fc3045acaeeR62 for Let me know if anything is missing in my explanation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, if the checks are for the value being set rather than empty, that would explain that. Thanks!
Closing this in favor of #34628 |
Addresses rdar://71240426