-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Don't link libc++ or libstd++ for Embedded Swift #7357
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
Conversation
These libraries are not usually available for embedded platforms. A workaround of passing this flag via `unsafeFlags` in `Package.swift` still remains after this change.
@swift-ci test |
// Don't link unavailable libc++ or libstd++ when building for Embedded Swift | ||
if !buildProduct.product.targets.contains(where: \.underlying.isEmbeddedSwiftTarget) { |
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.
I don't think C++ runtime library is unavailable for all Embedded platforms. For example, it seems like Pico SDK provides libc++: https://github.com/ARM-software/LLVM-embedded-toolchain-for-Arm
So it might be worth mentioning that in such case we ask users to explicitly specify desired C++ runtime via Xlinker
.
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.
I've expanded the comment removing the word "unavailable", with potential solutions suggested there as well.
@swift-ci test |
@swift-ci test windows |
6 similar comments
@swift-ci test windows |
@swift-ci test windows |
@swift-ci test windows |
@swift-ci test windows |
@swift-ci test windows |
@swift-ci test windows |
These libraries are not usually available for embedded platforms. A workaround of passing this flag via `unsafeFlags` in `Package.swift` still remains after this change.
These libraries are not usually available for embedded platforms. A workaround of passing this flag via `unsafeFlags` in `Package.swift` still remains after this change.
These libraries are not usually available for embedded platforms. A workaround of passing this flag via
unsafeFlags
inPackage.swift
still remains after this change.