-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Runtimes: properly link in swiftrtT?.obj
on Windows
#80101
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
@swift-ci please smoke 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.
I sense that this line will continue to grow and be a source of bugs as we try to keep everything in sync. Can we instead create an interface library (maybe SwiftRuntimeRegistration
) that forwards the link of the appropriate swiftrt?
Then replace these with
...
swiftCore
SwiftRuntimeRegistration
...
@swift-ci please smoke test |
@swift-ci please smoke test |
`swiftrtT.obj` should be used for statically linking the standard library (or within the standard library itself). For the other modules, we need to differentiate between `swiftrt.obj` and `swiftrtT.obj`. This fixes that oversight. This was not caught by the CI builds as we do not currently build both the static and dynamic variants of the new runtimes.
@swift-ci please smoke test |
swiftrtT.obj
should be used for statically linking the standard library (or within the standard library itself). For the other modules, we need to differentiate betweenswiftrt.obj
andswiftrtT.obj
. This fixes that oversight. This was not caught by the CI builds as we do not currently build both the static and dynamic variants of the new runtimes.