You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When following the documentation for macOS it's (almost) possible to compile everything but some test running and the end and ngscopeclient itself refuse to run with ERROR: [Loader Message] Code 0 : vkCreateInstance: Found no drivers!.
This probably happens because vulkan has to go through MoltenVK to run on the Metal drivers available on macOS and these aren't loaded if only VULKAN_SDK and PATH are updated. I had to source setup-env.sh from ~VulkanSDK/1.3.231.1/ which also sets a few additional VK_ variables to point towards MoltenVK. Everything works fine then. This should probably be added to the documentation.
The text was updated successfully, but these errors were encountered:
You are right, and it should also be reflected in the CI script. Currently we have the documentation, CI script and reality all having different processes. They should all be the same, working, process to build and run ngscopeclient.
Should be fixed by #81 (which covers installation/loading of prerequisites and the SDK), and ngscopeclient/scopehal-apps#673 (which ensures that molten-vk has been installed at build-time).
When following the documentation for macOS it's (almost) possible to compile everything but some test running and the end and ngscopeclient itself refuse to run with
ERROR: [Loader Message] Code 0 : vkCreateInstance: Found no drivers!
.This probably happens because vulkan has to go through MoltenVK to run on the Metal drivers available on macOS and these aren't loaded if only
VULKAN_SDK
andPATH
are updated. I had tosource setup-env.sh
from~VulkanSDK/1.3.231.1/
which also sets a few additionalVK_
variables to point towards MoltenVK. Everything works fine then. This should probably be added to the documentation.The text was updated successfully, but these errors were encountered: