@ptxmac LMK if there's a better forum to discuss this, but I'm seeing some strange behavior.
The libMoltenVK.dylib seems to behave differently if it's packaged with my app on its RPATH vs in /usr/local/lib.
When I package it with my application, at runtime it says that it is missing VK_KHR_get_physical_device_properties2. When I have it installed in /usr/local/lib it works as expected.
I've also tried linking statically against libMoltenVK.a, same results.
Ah I figured this out. I was linking the library properly, but at runtime the Vulkan code looks for /share/vulkan/icd.d/MoltenVK_icd.json. I'm now trying to figure out how to package that with a go binary.
@ptxmac LMK if there's a better forum to discuss this, but I'm seeing some strange behavior. The libMoltenVK.dylib seems to behave differently if it's packaged with my app on its RPATH vs in /usr/local/lib.
When I package it with my application, at runtime it says that it is missing
VK_KHR_get_physical_device_properties2
. When I have it installed in /usr/local/lib it works as expected.I've also tried linking statically against libMoltenVK.a, same results.
LMK if you have any idea what's going on. Thanks!