On Sun, Dec 10, 2017 at 3:09 PM, Kjetil Matheussen <k.s.matheussen@gmail.com> wrote:

My point is that when the jack server is started, it writes the path to the jack libraries somewhere global, and removes it when it shuts down. This way all clients will use the same libraries.

 
And to clarify some more: The only difference for the user compared to the current situation, is that the user doesn't have to install jack. If the user wants to upgrade jack, the user only have to download the latest version of qjackctl (or similar software). Normal clients doesn't have to include the jack libraries, only programs that wants to start the server have to include the jack libraries.


And of course, it should be like this for Linux and OSX as well. I'm mainly just proposing this as a way to work around the problem with the current installer in windows which (most probably) can't be cross-compiled.