azonenberg changed the topic of #scopehal to: ngscopeclient, libscopehal, and libscopeprotocols development and testing | https://github.com/ngscopeclient/scopehal-apps | Logs: https://libera.irclog.whitequark.org/scopehal
<_whitenotifier-f> [scopehal-apps] juh2600 forked the repository - https://github.com/juh2600
<juh> ...are libglm-dev, libglew-dev, glslang-dev, libglfw3-dev still required to build ngscopeclient:main? i thought opengl was officially phased out a while back, though i'm not really up on the whole graphics pipeline thing still
<juh> but i see them still listed in the manual
<juh> i'll find out soon enough!
sgstair has quit [Read error: Connection reset by peer]
<_whitenotifier-f> [scopehal] juh2600 forked the repository - https://github.com/juh2600
<juh> wait, this manual also refers to glscopeclient/scopehal-apps.git, this can't be up to date...
<azonenberg> juh: which manual are you using
<azonenberg> as far as requirements, yes. glm is a general math library, not opengl specific
<azonenberg> libglew should no longer be needed
<azonenberg> glslang is used because we are writing our shaders in GLSL (one of two languages supported for vulkan shaders, the other being directx's HLSL)
<azonenberg> and despite the name, glfw also supports vulkan and is what we use for window setup and creation
<juh> so just libglew that shouldn't be there anymore?
<azonenberg> oh i didnt merge bvernoux's PR yet apparently
<azonenberg> the readme link is out of date i thought i had fixed it everywhere
<azonenberg> the correct manual is on https://www.ngscopeclient.org
<azonenberg> and is probably a week or two behind the scopehal-docs git version but should be unchanged wrt build instructions
<juh> mind if i ask a more dev-nooby question? whaaat's the right way to "fork" this for dev/fiddling, given all the submodules? I went through and basically forked all the submodules until the clone worked, but that doesn't seem right
<juh> am i supposed to just clone the github org's copy, fork the repos i want to work on, and then update the remotes for my local copies to point to the forks?
<juh> fired up my fresh build of ngscopeclient and i got "could not load font file" so i want to double check that i built it right lol
<azonenberg> Submodules do unfortunately make it tricky. We use relative paths
<azonenberg> So if you fork *all* of the submodule repos, your local working copy should reference your local fork of every other submoudle
<azonenberg> unfortunately there's not a great way to fork some but not all of them
<azonenberg> Then you can explicitly pull from the upstream URL to sync your fork with upstream
<_whitenotifier-f> [scopehal-apps] azonenberg closed pull request #631: Update README.md (Add website / fix User Manual to use https://www.ngscopeclient.org) - https://github.com/ngscopeclient/scopehal-apps/pull/631
<_whitenotifier-f> [scopehal-apps] azonenberg pushed 2 commits to master [+0/-0/±2] https://github.com/ngscopeclient/scopehal-apps/compare/8b120d59a8fd...96f814e4e76d
<_whitenotifier-f> [scopehal-apps] bvernoux 9db3323 - Update README.md Added main website https://www.ngscopeclient.org Fixed link to latest user manuals / Getting Started (on https://www.ngscopeclient.org)
<_whitenotifier-f> [scopehal-apps] azonenberg 96f814e - Merge pull request #631 from bvernoux/master Update README.md (Add website / fix User Manual to use https://www.ngscopeclient.org)
<juh> so just forking all the submodules is the best move at the moment?
<azonenberg> Yeah
<juh> copy that o7
<azonenberg> All of the ones under the ngscopeclient org at least
<juh> ahh so things external to the org should be linked to their proper owners then
<azonenberg> submodules under my personal account can be left as absolute URLs unless you plan to fork them but most of those are very simple wrappers you shouldnt have to mess with unless you're doing some kind of porting work
<azonenberg> Yeah exactly
<azonenberg> submodules within the org use relative paths so you have to basically mirror that
<azonenberg> the reason for this is, if you use absolute paths you have to use https or git urls
<azonenberg> and git urls are more convenient for devs, but can't be cloned by anyone without a valid github account
<azonenberg> so we transitioned from absolute to relative paths with this as a consequence
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 255 seconds]
Degi_ is now known as Degi
<juh> ahh, my missing fonts were from a persisted ~/.config/ngscopeclient/preferences.yml from my last distro, when i'd built it under a different path. app now opens /o/
<juh> and have confirmed that newly generated preferences.yml refs /usr/* instead of /home/*, since i was looking at #624 which looked related and similar but for macos
<azonenberg> So that might be an installation bug. In general FindDataFile() has a list of paths it looks for
<azonenberg> InitializeSearchPaths() in lib/scopehal/scopehal.cpp makes this list
<azonenberg> the default preference init code calls FindDataFile() to find files in the fonts directory
<azonenberg> but if it's failing to find fonts it's almost certainly going to also fail to find toolbar icons, shaders, and every other external resource
<azonenberg> (unless the prefs file is borked somehow)
<azonenberg> (we should probably test for and ensure we gracefully degrade to the imgui builtin bitmap font if a preference fails to load a font
<juh> ok, finally got it somewhat connected to rigol, as we all know it is not having a good time :D
<juh> i'll try to document what specifically makes this feel so awkward so we can strategize with that info
<azonenberg> Yep
<azonenberg> in general improving the "out of box experience" is the #1 item on my priority list for the v0.1 release
<azonenberg> this includes outright failures to build/install, lack of binary packaging, crashes, data corruption, missing/incomplete/inaccurate documentation
<azonenberg> anything that makes it hard for someone to get moving quickly and painlessly
<_whitenotifier-f> [scopehal-apps] azonenberg pushed 1 commit to master [+0/-0/±1] https://github.com/ngscopeclient/scopehal-apps/compare/96f814e4e76d...41e0583c4ac8
<_whitenotifier-f> [scopehal-apps] azonenberg 41e0583 - Session: fixed bug where trying to load a session online did not correctly degrade if the instrument socket connection fails
_whitenotifier-f has quit [Ping timeout: 245 seconds]
sgstair has joined #scopehal
_whitenotifier-b has joined #scopehal
<_whitenotifier-b> [scopehal-apps] azonenberg pushed 1 commit to master [+0/-0/±2] https://github.com/ngscopeclient/scopehal-apps/compare/41e0583c4ac8...ecc525e6d344
<_whitenotifier-b> [scopehal-apps] azonenberg ecc525e - "Manage instruments" dialog now correctly handles offline instruments