Neither the official dx headers 1 nor dxvk 2 set __stdcall, however vkd3d-proton does 3.
This wouldn't necessarily be a problem if one sticks only to using vkd3d-proton, however it does become quite tricky to correctly use vkd3d-proton along with dxvk's dxgi in the same project.
Would it be acceptable to use the default abi for native builds, or make this configurable at build time?
It's a vestigal thing from when vkd3d was implemented in native code rather than PE, so if you know how to modify the widl invocation to avoid ms_abi, feel free to propose a PR.
Neither the official dx headers 1 nor dxvk 2 set
__stdcall, however vkd3d-proton does 3.This wouldn't necessarily be a problem if one sticks only to using vkd3d-proton, however it does become quite tricky to correctly use vkd3d-proton along with dxvk's dxgi in the same project.
Would it be acceptable to use the default abi for native builds, or make this configurable at build time?