On Sun, December 10, 2017 14:33, Kjetil Matheussen wrote:
> On Sun, Dec 10, 2017 at 2:19 PM, Thomas Brand <tom@trellis.ch> wrote:
>
>
>> On Sun, December 10, 2017 14:11, Filipe Coelho wrote:
>>
>>> On 10.12.2017 14:09, Thomas Brand wrote:
>>>
>>>
>>>> On Sun, December 10, 2017 14:03, Filipe Coelho wrote:
>>>>
>>>>
>>>>> On 10.12.2017 12:24, Thomas Brand wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Can we get a non-RC release for X-Mas, please?
>>>>>>
>>>>>>
>>>>>>
>>>>> I don't see why not :)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> I was trying to get windows builds working, but got sidetracked
>>>>> with other stuff. The release notes are already done, I will do
>>>>> this soon.
>>>>>
>>>> +1 for windows build! so that we have the same shiny version on
>>>> linux and windows. I hope that non-critical pull-requests will find
>>>> the way into the release.
>>>
>>> I think I was not clear enough.
>>>
>>>
>>>
>>> I was not able to get windows builds. I don't even got to update my
>>> mingw build. 1.9.12 is kinda tagged already (just not officially). So
>>> 1.9.12 *will not have windows or macOS builds*.
>>>
>>>
>>
>> hm, ok .. I'm speculating that
>> "Kjetil Matheussen" <k.s.matheussen@gmail.com>
>> could help you there. It would make most sense to have at least one
>> other supported platform so that it's "multi"-platform. For an audio
>> abstraction layer like JACK it's even more important since
>> multi-platform makes the abstraction complete. Cheers
>>
>>
>>
> The windows versions of Radium has included a custom version of jack
> 1.9.12
> since october. If you want to manually upgrade jack on your windows
> machine, it might work just to replace the old jack files with the one
> included in Radium. As I've expressed before, the installer should be
> removed, and jack should be installed locally for all programs wanting to
>  use it. This will not break any programs. Radium partly does this
> already. Radium first checks if Jack is installed globally, and if not, it
> uses the version of jack installed in the "jack_local" directory. But for
> this to work properly with more than one client, jack needs to inform
> where the currently used libraries are placed so that different clients
> aren't using different versions of the jack libraries.
>

This sound sort of crazy, but why not just wrap an nsis installer around
your 1.9.12 build?