Emi
Amazing! You rock!
Re-opening because people are hitting into this in other cases: https://www.reddit.com/r/Zig/comments/146avyi/error_no_field_named_x_in_struct_y_despite_field/ Maybe it's not the compiler's job to tell users about this - but there should probably be some answer...
I should also note, we have regressed here slightly in 6f42876e74831b7f9cecf5a863634df920c52b98 (although that change is not to blame for the issue here) x86_64-macos -> x86_64-linux with Mach engine worked prior...
Pay close attention to the `zig build-exe` invocation: ``` /usr/local/bin/zig build-exe [...] -I /usr/local/Cellar/libx11/1.7.3.1/include -I /usr/local/Cellar/libxcb/1.14_2/include -I /usr/local/Cellar/libxau/1.0.9/include -I /usr/local/Cellar/libxdmcp/1.1.3/include -I /usr/local/Cellar/xorgproto/2021.5/include -L /usr/local/Cellar/libx11/1.7.3.1/lib [...] ``` I don't know for...
I checked on a recent Zig version, and following the reproduction steps in the issue description I can still reproduce this in a small example: > zig build -Dtarget=x86_64-linux-gnu --verbose...
@marler8997 I am discovering mingw-w64 headers are missing key updates to the Direct3D 12 headers, and the latest D3D12 headers from the Windows SDK are incompatible with mingw-w64's COM definitions...
@andrewrk Yeah, this was the first thing I checked actually. Unfortunately, latest mingw-w64 headers do not fix this. I will see about filing issues upstream on mingw-w64 Here are some...
@michal-z The primary problem isn't that the d3d12.h is outdated, I can workaround that by including updated d3d headers as you noted. The big problem is those last two bullet...
Lengthy write-up incoming, hoping this is useful to whoever else stumbles across this issue and attempts to solve it. After spending ~2 weeks on this, I don't feel I've made...
@michal-z Ah, yes, I forgot to mention vk3d-proton. I did look into this as well. I do believe they are compatible with Wine's WIDL. However, they are actually quite stripped...