<d1b2>
<dingwat> @fredzo_72653 i may have figured out a way to get WiX installed via choco, still fighting some issues in the workflow on my fork but maybe this is an acceptable way to get WiX on the runner?
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #scopehal
Degi has quit [Ping timeout: 272 seconds]
Degi has joined #scopehal
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #scopehal
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #scopehal
<d1b2>
<genialeprutser> "people willing to compile from source are probably able to spend some time poking at the code when things go wrong and not need a lot of handholding getting started" I am a new developer. New in the sense that I don't know this code base, experienced in the sense that I know about dynamic linking, and where to find dll's on Windows. If I follow the steps in the manual to compile it for the first time, and it fails, then I'm tempted to
<d1b2>
leave. If I ask about it on the forum and don't get help, I'm more tempted to leave. Thankfully I did get a lot of help, so I am staying.
d1b24 has joined #scopehal
d1b2 has quit [Read error: Connection reset by peer]
d1b24 is now known as d1b2
<d1b2>
<fredzo_72653> Sure! Whatever is working! What version of Wixtoolset is it ? Version 3 ? CPack only supports version 3 (except for cmake 3.30 which is not yet available from pacman).
fayr has quit [Ping timeout: 276 seconds]
fayr has joined #scopehal
<d1b2>
<fredzo_72653> @azonenberg / @david.rysk is there any particular reason why we are running Windows CI build on 3 environments (clang64, mingw64 and ucrt64) ? CPack/WiX will not run on clang64 (requires gcc) and mingw64 seems a bit outdated (see here: https://stackoverflow.com/questions/76552264/what-are-msys2-environments-how-do-i-pick-one). Would it be OK to only keep urct64 (which is the one recommended by the Getting Started documentation and that we
<d1b2>
use (at least I use:-) for development) ?
<d1b2>
<david.rysk> the reason was that the different environments tend to show different compiler warnings/errors
<d1b2>
<david.rysk> mingw64 is a bit outdated, but we've had people complain about needing to install the redist...
<d1b2>
<azonenberg> For generating CI binaries for people to use (and eventual release artifacts) only one windows build environment is sufficient IMO
<d1b2>
<azonenberg> so if ucrt64 is the easiest, fine by me
<d1b2>
<azonenberg> can we keep the others for general testing and just not build a MSI on them?
<d1b2>
<azonenberg> Yeah this wasn't an intentional goal to drive people away so much as "we have limited resources and during early stages, we should prioritize development rather than bringing in new users we lack the resources to support"
<d1b2>
<azonenberg> as the community grows and docs improve we can handle a larger userbase
<d1b2>
<azonenberg> anyway, as of now we have CPack generating deb packages on ubuntu/debian (ubuntu in CI, debian has to be manually built offline for now but eventually i want to set up a self hosted debian runner again)
<d1b2>
<azonenberg> RPM should be straightforward to add, if we have anyone using an RPM-based distro who can test and help figure out the list of package names for dependencies
<d1b2>
<azonenberg> and then i need to poke lain, she was gonna help with macos packaging
<d1b2>
<fredzo_72653> OK so thank's to @dingwat suggestion to use chocoloatey to install WiX on github Windows box I might have a working build for Windows MSI installer 🥳 I'll check if I can keep mingw64 and clang64 for build only.
<d1b2>
<azonenberg> woo
<dingwat>
yay nifty. I'm confused because I cannot get the clang64 build to run on my fork, but it's completing on the main repo?
<d1b2>
<dingwat> @fredzo_72653 for whatever reason, it's failing in the build step with a "gcc not found" error, despite me not changing the dependencies
_whitelogger has joined #scopehal
<d1b2>
<dingwat> @fredzo_72653 anyway, if you've got a working workflow, great. Mine is only succeeding on mingw64, but I did get an installer that seems to work
<d1b2>
<fredzo_72653> The "gcc not found" message comes from WiX packaging, you must have set WIXPATH variable and it tries to create MSI installer except gcc is not available in clang
<d1b2>
<azonenberg> will test and merge later today
<d1b2>
<azonenberg> that's a nice milestone
<dingwat>
awesome
<d1b2>
<prostephenfalken> Hello everyone! Sorry to bother. A quick question: While installing in MacOS x86_64 I've required to install "hidapi" but I can't see this mentioned in the Installation Instructions. Shall I open a PR adding it to the Basic Requirements for MacOS?
_whitelogger_ has quit [Remote host closed the connection]
<d1b2>
<azonenberg> yeah i just havent gotten around to compiling the docs and pushing updated renders to the website
<d1b2>
<azonenberg> because i have a bunch more changes to make
<d1b2>
<azonenberg> enough people have complained about the hidapi issue i should do an update soon though
<d1b2>
<macaba> Heh, I had to check the tex today to fix that Very issue
<d1b2>
<azonenberg> anyway i'm busy with $dayjob and about to have lunch and get the mail, but later on i'll review and merge the msi PR and then can work on getting updated doc renders pushed to the website
<d1b2>
<azonenberg> We're still waiting on packaging for macos arm64 ( @lainpants is supposed to be helping me with that but has been busy) as well as getting CPack configs for RPM distros
<d1b2>
<azonenberg> and then i have to check if we're uploading portable linux binaries as artifacts yet
<d1b2>
<azonenberg> if not, that should be better than nothing for distros like arch that aren't deb or rpm based
<d1b2>
<fredzo_72653> @azonenberg if you can merge this one before pushing the updated doc on the website ?: https://github.com/ngscopeclient/scopehal-docs/pull/102 It removes the misplaced hid-api dependency from Vulkan dependencies section on Windows Getting Started guide.