Problems building for Windows x64 using Visual Studio 17.11.0 #808
Comments
|
It seems that the error message that you are trying to search for might be one of: All of these cases seem to indicate an issue where the C++ standard library is unhappy about some path through the standard library. |
|
I think that was recently introduced in 17.11.0. A temporary workaround might be to use 17.10.0 (though we will need to figure out what is going on here). |
|
I think that this might be a bug in the older clang that we use for bootstrapping. It seems to work with the newer compiler. However, that uncovers another bug in build.ps1 :( |
|
Thanks for the quick responses. You just saved me a bunch of time. I’ll get back to this next weekend and see if I get further. Is there a way to use the Clang standard library headers when compiling and bypass those provided by Visual C++, or will that open up a different kettle of fish.
From: Saleem Abdulrasool ***@***.***>
Sent: Sunday, August 18, 2024 7:56 PM
To: compnerd/swift-build ***@***.***>
Cc: glenrgordon ***@***.***>; Author ***@***.***>
Subject: Re: [compnerd/swift-build] Problems building for Windows x64 using Visual Studio 17.11.0 (Issue #808)
I think that this might be a bug in the older clang that we use for bootstrapping. It seems to work with the newer compiler. However, that uncovers another bug in build.ps1 :(
—
Reply to this email directly, view it on GitHub <#808 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEMY6EPWPG6BZRO6YKEADPLZSE7DZAVCNFSM6AAAAABMWZADA6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGQ4DCMJSGU> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AEMY6EK4GJGMUSWGIXPRSBLZSE7DZA5CNFSM6AAAAABMWZADA6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUI2JBSK.gif> Message ID: ***@***.*** ***@***.***> >
|
|
No, not currently; we build the compiler against the windows system libraries and compilers. The problem is that the SwiftCompilerSources is Swift code which falls back to the integrated clang. |
|
Could it help if a 6.0 toolchain like this is used as the pinned (bootstrap) toolchain? |
|
@hjyamauchi we cannot pin the toolchain to 6.0 as the 5.10 toolchain is the agreed upon bootstrap toolchain for the project. |
|
@compnerd Would it make sense to need to pin the VS version like the Swiftlang CIs then? |
|
Well, I'd rather not pin the VS version for main - that needs to be fixed. |
|
fix (pending deployment): swiftlang/llvm-project#9153 |
Trying to build Swift for windows for the first time. 30+ years as Windows developer, brand new to Swift.
I'm using the commands:
repo sync
S:\SourceCache\swift\utils\build.cmd -WindowsSDKs x64 -DebugInfo -SkipPackaging -EnableCaching
No problems till I get to building the basic module. Looks to me that Clang can't parse something from the complex header file but I can't figure out what or why.
Output follows. Any help in at least understanding what might be going wrong would be great. Am wanting to contribute to Swift on Windows, but obviously need to be able to build first.
Let me know if there's other info that I can provide to help diagnose what I must be doing wrong.
Thanks
The text was updated successfully, but these errors were encountered: