runtime: add a workaround for Windows build #27196
Conversation
The runtime tests will statically link the runtime and dynamically link to the standard library. This fails to build on Windows. This is a horrible workaround for the time being.
|
@swift-ci please smoke test |
|
@swift-ci please test Windows platform |
|
CC: @jckarter |
|
IIRC there's a macro that's defined while building the runtime for the standard library. Could we conditionalize this on that macro so we don't need |
|
@jckarter - I would love to do that. This seems fundamentally wrong. However, I don't think that we build the runtime twice, so I'm afraid that Im not following what you are suggesting. |
|
Hm, I thought we did rebuild the runtime object files when building for SwiftRuntimeTests, because there have been other linking problems that we've needed to deal with due to the different requirements of SwiftRuntimeTests vs. everything else, but maybe I'm mistaken. |
|
Going to merge this for now, I'll take a look into that and adjust it if I can. |
The runtime tests will statically link the runtime and dynamically link
to the standard library. This fails to build on Windows. This is a
horrible workaround for the time being.
Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.
Resolves SR-NNNN.