Martin Storsjö

If you have a look at the commit I linked to you, apparently it just checks whether the target architecture is different, so it doesn't think x86_64 linux -> x86_64...

Many build tools try to avoid such long paths when they are building on actual Windows, by storing the command line in a `.rsp` file, and passing that like `@args.rsp`....

> So I could make changes to the wine-msvc.sh to get it to compile. I had an error in the previous code that's fixed now. But it's still pretty, pretty...

> So I am wondering why you not "simply" use the Windows build of cmake? Shouldn't that fix this issue by itself? If you want to use the Windows build...

Yes, `--skip-recommended` is hard to use with wine - I've tried to minimize the install with it, but before you get wine back into working condition, you essentially have used...

> The clang backend seems to be very sensitive about SEH directives. I keep hitting an issue where the length of the function can't be determined: > > ```shell >...

Also, some minor comments on earlier posts here: > I have generated some example assembly code (clang -S), yet the generated assembly uses a relocation scheme based on a fixed...

> I did notice that EH in CLANG looked to use the UCRT handlers. Maybe this won’t be a problem for any LLVM based projects. GCC has its own EH....

> > link against debug version of the UCRT using this toolchain? > > Do you mean ucrtbased.dll? In mingw-w64 UCRT, programs are not directly linked with ucrtbase.dll but with...

> > Assuming that ucrtbase.dll and ucrtbased.dll export pretty much the same symbols, you can make a copy of ucrtbase.def.in and change it to say “LIBRARY ucrtbased.dll”, hook it up...