On Wed Mar 12 19:19:26 2025 +0000, Nikolay Sivov wrote:
Well sure, I'm talking about vkd3d-shader side already, whether we want this option exposed and documented for any vkd3d_shader_compile() user, or make it into something internal. I don't see how any end user of vkd3d-shader, outside of wine, would think of using any of those custom options. Also I'm surprised we ended up having any logic involving windows module version numbering in vkd3d-shader.
It's in vkd3d-utils though, not vkd3d-shader.
The `compiler_version` argument to `D3DCompile2VKD3D()` seems pretty reasonable to me, each _xx version effectively represents a separate API. Sometimes they happen to match, but sometimes not, which leads to needing to pass different vkd3d-shader flags depending on the version.