-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fix linking error on linux #9306
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
daveinglis
commented
Oct 29, 2025
- libstdc++ needs to be added when linking if any dependency has a cpp dependency
|
@swift-ci test |
b71befd to
27bcc50
Compare
|
@swift-ci test |
|
@swift-ci test windows |
27bcc50 to
3e1e26a
Compare
|
@swift-ci test |
|
@swift-ci test windows |
|
This seems more appropriate to be done at the Swift Build level - @owenv, what do you think? |
|
Maybe. Could this be modeled using impartedSettings instead of manually propagating the flags from dependency to dependent? |
|
ah, ya, let me try the impartedSettings to see if that will work, forgot about that as a way to pass settings up the chain |
3e1e26a to
6f87ef9
Compare
|
@swift-ci test |
|
@swift-ci test windows |
|
@swift-ci test macos |
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.
lgtm assuming tests pass
- libstdc++ needs to be added when linking if any dependency has a cpp dependency
6f87ef9 to
8c8cebf
Compare
|
@swift-ci test |
|
@swift-ci test windows |
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.
Nice, much cleaner. I think this sort of thing should probably still be handled at the Swift Build level, but this seems fine as an immediate fix.
|
@swift-ci test windows |