macOS_Wine_builds VS DirectXShaderCompiler

Hi, I followed this guide of u/Gcenx https://github.com/Gcenx/WineskinServer/issues/420 and applied on wine 8.10 staging (this version https://github.com/Gcenx/macOS_Wine_builds/releases/tag/8.10) but it seems like it doesn't work I always get a stub error. My question is: I need to do something else or D3DMetal simply doesn't work on newer wine version

The new Winehq macOS packages can be found https://github.com/Gcenx/macOS_Wine_builds/releases these will work on macOS High Sierra (10.13) and later.

Not sure where you got your wine binaries from, but wine-staging from this brew tap has the fix.

Gcenx maintains macOS builds of Wine that are as close to WineHQ releases as possible alongside other versions. https://github.com/Gcenx/macOS_Wine_builds They do work on Ventura although I believe 32-bit apps are still not working at the moment.

Depending on if you have an Intel Mac or an M1 Mac, you have some different options! If you have an M1 Mac, you could try using Wine/Wineskin Winery. You could also try something like UTM, but it's probably going to be very slow. If you find some of these games as old Mac games instead of old Windows games, you might also be able to get them running through SheepShaver or BasiliskII. If you're on an Intel Mac, your two best bets are VirtualBox or maybe, like, Windows 10 on Boot Camp.

u/gcenx maintains newer builds from macOS on GitHub. 64-bit Wine 7.x is also available from nixpkgs (32-bit support won’t be available until it’s possible to build WoW64 on Darwin).

There are builds of wine 7 you can get through brew, but I think it's maybe an uphill battle: https://github.com/Gcenx/macOS_Wine_builds

Actually the current macOS packages are not being pushed to Winehq directly due to an unresolved bug, they can be found https://github.com/Gcenx/macOS_Wine_builds

If you want wine-7.0 I’ve provided a package that will function https://github.com/Gcenx/macOS_Wine_builds/releases/download/7.0/wine-stable-legacy-7.0-osx64.tar.xz.

> We may support DXBC generation in Clang in the future (we mentioned that in the original proposal to LLVM). That work is unlikely to begin for a few years as our focus will be on supporting DXIL and SPIR-V generation first.

I appreciate this quote[0] from the microsoft camp. Setting clear expectations that something will not be done is a nice bit of fresh air.

[0] https://github.com/microsoft/DirectXShaderCompiler/issues/57...

There's no need for transpilers these days, you can just compile HLSL to SPIR-V bytecode with dxc.

https://github.com/microsoft/DirectXShaderCompiler

Use DXC and only HLSL for your main shader editing.

You can see libdxilconv in there, DXIL is the DirectX Intermediate Representation, documented in the open source shader compiler from Microsoft.

BTW, this problem can be reproduced as described below: - clone https://github.com/SaschaWillems/Vulkan.git - build the project and run it with arguments : -v - s hlsl to enable the validation layer and to use hlsl code - run ComputeShader project. The following validation error "Type mismatch on descriptor slot ..." will be shown in the console. - to fix it, as suggested above, you can replace the 3rd line of emboss.comp, sharpen.comp, and edgedetect.comp from: Texture2D inputImage : register(t0); //Creates validation errors to RWTexture2D inputImage : register(u0); //no validation errors (you'll then need to recompile the shaders to spv with a proper hlsl compiler such as Microsoft dxc)

EDIT: There is also naga but it does not take HLSL as input: https://github.com/gfx-rs/naga but you can use DirectXShaderCompiler to compile to SpirV, then use naga to compile to Metal.

🤨 For a "refusal to acknowledge it", they do appear to have a rather sizeable document mapping between HLSL and SPIR-V? https://github.com/microsoft/DirectXShaderCompiler/blob/main/docs/SPIR-V.rst

I am starting work on a compute-driven rendering engine, and it seems that the best way to go around it will be to write code in HSSL, and then use DirectXShaderCompiler to generate SPIR-V, and SPIRV-Cross to then generate MSL. And while DXSC's repo has a page on incompatibilities, no such resource seems to exist for SPIRV-Cross targeting Metal.

DirectX Shader Compiler