-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[stubs] Autolink against icucore on Darwin. #9780
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
This reverts commit f1a7c3d.
This reverts commit 0de2425.
Programs using a statically linked build of the standard library need to explicitly link against icucore. There are various potential hacks^Wsolutions to this problem, and this is an attempt at a lesser of evils approach. Emit a linker directive to perform autolinking against icucore on Darwin systems. This allows us to avoid hacking the compiler driver and propagating that hack onto any build systems that don't go through the driver.
@swift-ci please test |
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.
Looks good to me. We should add -lc++
and -framework Foundation
in a follow-up commit too. (Unfortunately for us the only options supported are -l
and -framework
, IIRC.)
Build failed |
@swift-ci please test Linux Platform |
Build failed |
@swift-ci please test Linux Platform |
Build failed |
@swift-ci please test OS X platform |
(issue was unrelated and already fixed elsewhere) |
Programs using a statically linked build of the standard library need
to explicitly link against icucore. There are various potential
hacks^Wsolutions to this problem, and this is an attempt at a lesser
of evils approach.
Emit a linker directive to perform autolinking against icucore on
Darwin systems. This allows us to avoid hacking the compiler driver
and propagating that hack onto any build systems that don't go through
the driver.