Provide an autobuild for a Jamulus with JACK windows version.

[jujudusud]

I was thinking about the possibility to use JACK server on windows by building your own custom "jackonwindows" Jamulus.
I think we should provide a package (.exe installer) for windows of a version of Jamulus using JACK server on this OS since nearly 99% of Windows users just want to install software instead of build there own packages.

[henkdegroot]

I agree, most Windows users won't go and build their own packages.
Should this exe installer have a different name compared to the current installer?
Should there be a visual aspect in the app that is a "JACK" version instead of an "ASIO" version?

[ann0see]

should the installer with jack be as clever as the ASIO version and check if JACK is installed or not?

Definitly not a requirement, but would be nice. You could check if jack.exe exists and show a similar warning.

[henkdegroot]

You could check if jack.exe exists and show a similar warning.

ASIO check is based on a registry key, we can do the same thing for JACK. It does mean we need to add strings to the installer nsi files for all languages.

[henkdegroot]

It does mean we need to add strings to the installer nsi files for all languages.

To keep the introduction simple, I will setup my PR without this. It can always be added after to improve.

[henkdegroot]

@ann0see , I have a working solution for the scripts etc. The complete change will add deploy scripts for windows autobuild and a jack powershell script as well. To make the autobuild include this, the overall autobuild steps have to be updated as well. Can that all be done in 1 PR or should the "autobuild" update be a separate PR after the initial one has been merged?

[ann0see]

I‘d use one PR to keep it simple