-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[5.9] Enable macros on Windows #68743
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
[5.9] Enable macros on Windows #68743
Conversation
Use WiX to extract a future toolchain to allow building the macros support when building the toolchain. We build swift-syntax and now wire that into the build itself.
try a more recent toolchain
swiftlang/swift-installer-scripts#246 @swift-ci please build toolchain windows platform |
|
To be clear, I reverted all the substitution changes here. But given this is in lit.py and we already substitute T:, I could add back in the lit related ones? EDIT: I've added 7d13da4 in and will run with the LLVM lit changes as well. The other Swift changes are related to the source directory substitution. |
(cherry picked from commit 7d13da4)
swiftlang/llvm-project#7513 @swift-ci please build toolchain windows platform |
@bnbarham I think we need this change from your previous PR: This is what caused the expansion of the T:\ build directory I believe. |
I don't think we can take that one, or at least if we did we'd have to split it to do only the EDIT: Oh, of course this isn't true because we're not using a substitute drive for SOURCE_DIR any more. And this must work because main has those changes already. So... picking up that change. |
(cherry picked from commit 136642c)
swiftlang/llvm-project#7513 @swift-ci please build toolchain windows platform |
@hyp Any idea about this test failure? I'm out of my depth. It seems like the C++ interop method is called with typed instead of untyped parameters? 🤔
|
I'm not sure why this test is failing on this run of building the toolchain, perhaps this test is somehow missed by regular windows PR CI? In any case, this failure is due to the test assuming opaque pointer types are enabled in LLVM, but the 5.9 LLVM branch assumes that opaque pointer types are not enabled. I think it's fine to fixup the test case's CHECK line in this patch. |
swiftlang/llvm-project#7513 @swift-ci please build toolchain windows platform |
Thanks @hyp! Re-running with those changes now. |
5.9 has been running builds in CI without failing when tests failed, xfail the only failing test.
0b72f18
to
d1553c9
Compare
swiftlang/llvm-project#7513 @swift-ci please build toolchain windows platform |
Squashed cherry-pick of swiftlang#68334 and swiftlang#68743.
Squashed cherry-pick of swiftlang#68334 and swiftlang#68743.
Squashed cherry-pick of swiftlang#68334 and swiftlang#68743.
Use WiX to extract a future toolchain to allow building the macros support when building the toolchain. We build swift-syntax and now wire that into the build itself.