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: 268 seconds]
Degi_ is now known as Degi
josuah has quit [Remote host closed the connection]
azonenberg has quit [Ping timeout: 268 seconds]
azonenberg has joined #scopehal
Johnsel has joined #scopehal
Johnsel has quit [Ping timeout: 268 seconds]
Johnsel has joined #scopehal
<d1b2> <macaba> Thanks to all those who got the github CI to produce a working ngscopeclient-windows-portable - it runs here 🙂
<d1b2> <macaba> Also saw some discussion about the future. Ideally, so I can start contributing on windows, I've already spotted a good first bug for me to look at: - I could install a minimum number of support installers (maybe just vulkan SDK perhaps?). - I could check out the repo, open a visual studio solution file and just start the build/debugger immediately with no/minimal additional steps. (I sometimes wonder if software developers love arbitrary
<d1b2> complexity) - The total output size is much smaller than 1GB (least important though).
<azonenberg> macaba: so basically right now, we pull in a ton of other overhead because glscopeclient uses GTK and a ton of other heavyweight dependnecies that are hard to use under visual studio natively
<azonenberg> the plan was to not do too much more work on the windows build process until we had fully deprecated that
<azonenberg> Which basically means taking the last few features that are glscopeclient-only and implementing them in ngscopeclient before making a clean cutover
<azonenberg> at that point we can start doing a bunch of build environment and architectural cleanup that will be much easier vs trying to do in both tools (or impossible outright due to GTK etc)
josuah has joined #scopehal
bvernoux has joined #scopehal
Johnsel has quit [Ping timeout: 268 seconds]
Johnsel has joined #scopehal
<_whitenotifier-9> [scopehal-apps] bvernoux opened issue #596: ngscopeclient preferences.yml font path shall use relative path by default - https://github.com/glscopeclient/scopehal-apps/issues/596
<_whitenotifier-9> [scopehal-apps] bvernoux edited issue #596: ngscopeclient preferences.yml font path shall use relative path by default - https://github.com/glscopeclient/scopehal-apps/issues/596
<_whitenotifier-9> [scopehal-apps] bvernoux edited issue #596: ngscopeclient preferences.yml font path shall use relative path by default - https://github.com/glscopeclient/scopehal-apps/issues/596
<_whitenotifier-9> [scopehal-apps] bvernoux edited issue #596: ngscopeclient preferences.yml font path shall use relative path by default - https://github.com/glscopeclient/scopehal-apps/issues/596
<_whitenotifier-9> [scopehal] bvernoux opened pull request #779: Update scopehal.cpp FindDataFile to use relative path when possible - https://github.com/glscopeclient/scopehal/pull/779
<_whitenotifier-9> [scopehal-apps] bvernoux edited issue #596: ngscopeclient preferences.yml font path shall use relative path by default - https://github.com/glscopeclient/scopehal-apps/issues/596
<_whitenotifier-9> [scopehal-apps] bvernoux edited issue #596: ngscopeclient preferences.yml font path shall use relative path by default - https://github.com/glscopeclient/scopehal-apps/issues/596
<bvernoux> Pushed an other fix for scopehal to use relative path
<d1b2> <johnsel> bvernoux can you check demoscope on your end? it seems broken
<d1b2> <johnsel> at least on Windows
<bvernoux> it works here
<bvernoux> johnsel what is your issue with which version ?
<bvernoux> with latest fix again FFTS is broken
<bvernoux> it is an alignment issue ...
<bvernoux> so it is pretty random
<bvernoux> ngscopeclient demo work for me with the commit 2f4cf45
<bvernoux> like said it is pure luck and it is because of FFTS alignment issue with stack / windows(gcc/mingw64) ...
<bvernoux> 10 years that bug is here and no solution so far
<bvernoux> there is not such issue on Linux because the stack is not managed the same way ...
<bvernoux> and ensured to be aligned IIRC ...
<bvernoux> on ngscopeclient FFTS is used only for demo to generate some signals IIRC
<bvernoux> I think there is WIP to replace all ffts crap with VkFFT
<bvernoux> Look into replacing FFTS calls with vkFFT
<bvernoux> I'm not sure lainy is working on that in fact
<d1b2> <johnsel> bvernoux it's 335945e
<bvernoux> Could you tell what does not work ?
<bvernoux> I suspect it is just when you do Play on Demo
<bvernoux> which crash on the FFTS
<d1b2> <johnsel> oh now it works again
<d1b2> <johnsel> random crashing indeed then
<bvernoux> yes the ffts crap is awful
<bvernoux> it depends on some alignment
<bvernoux> ffts does not work are all on MacOS too
bvernoux has quit [Quit: Leaving]