azonenberg changed the topic of #scopehal to: libscopehal, libscopeprotocols, and glscopeclient development and testing | https://github.com/glscopeclient/scopehal-apps | Logs: https://libera.irclog.whitequark.org/scopehal
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 258 seconds]
Degi_ is now known as Degi
balrog has quit [Quit: Bye]
balrog has joined #scopehal
<d1b2> <svenpeter42> just compiled scopehal-apps on apple silicon and it didn't quite work at first. I had to cd to VulkanSDK/1.3.231.1/ and source setup-env.sh
<d1b2> <svenpeter42> just exporting VULKAN_SDK and PATH like in the documentation resulted in "ERROR: [Loader Message] Code 0 : vkCreateInstance: Found no drivers!"
<d1b2> <svenpeter42> should I open an issue on github about that? or create a PR for the documentation?
bvernoux has joined #scopehal
bvernoux has quit [Read error: Connection reset by peer]
<d1b2> <johnsel> export VULKAN_SDK=~/VulkanSDK/1.3.231.1/macOS
<d1b2> <johnsel> did you have VulkanSDK installed in that directory?
<d1b2> <johnsel> I guess the docs leave it up to your own determination where you put things
<d1b2> <johnsel> it may be the default of the installer
<d1b2> <johnsel> or maybe let's start with is it it macos?
<d1b2> <johnsel> I do see see things in the macos CI I don't like (CI doesn't reflect the installation process you'd use locally but uses some stripped Vulkan SDK plugin)
<d1b2> <johnsel> if the getting started documentation expects you to install to a certain directory but doesn't make that explicit it's a problem too
<d1b2> <johnsel> it's also not nice to expect fixed installation paths for SDKs in ~
<d1b2> <johnsel> but @svenpeter42 are you on mac os on apple silicon on linux on macos silicon?
<d1b2> <svenpeter42> mac os apple silicon
<d1b2> <svenpeter42> and vulkan sdk is in that directory
<d1b2> <svenpeter42> i suspect it needs VK_DRIVER_FILES (or any of the other defines setup-env.sh) sets as well
<d1b2> <svenpeter42> compiling also worked fine, it just failed when it tried to run some test and the ngscopeclient binary also wouldn't launch
<d1b2> <johnsel> Yes seems it's a driver side issue
<d1b2> <johnsel> feel free to PR the change
<d1b2> <johnsel> although actually make that an issue
<d1b2> <johnsel> I want to modify the CI script too to actually run the instructions we expect users to run
<d1b2> <johnsel> then it catches things like this
<d1b2> <johnsel> or do both, 🙂
juri_ has joined #scopehal