On Monday 18 April 2011, David Henningsson wrote:
> Ok, I don't mind compiling in JackWeakAPI.c into FluidSynth for the
> Windows build.
I don't mind either, if it can be compiled with MSVC too.
Regards,
Pedro
___
fluid-dev mailing list
fluid-dev@non
Le 18 avr. 2011 à 11:38, David Henningsson a écrit :
> On 2011-04-18 10:35, Stéphane Letz wrote:
>>
>> Le 18 avr. 2011 à 08:47, David Henningsson a écrit :
>>
>>> Hi Graham,
>>>
>>> I don't want to push the problem back and forward, but in this case I think
>>> it's reasonable to say that:
>>
Hi David,
> Ok, I don't mind compiling in JackWeakAPI.c into FluidSynth for the
> Windows build. I'm not sure how this relates to ASIO though, it seems
> like an unrelated problem...?
Having Jack for Windows is the solution to the current ASIO driver
issue. jOrgan's libfluidsynth dll can't be dis
On 2011-04-18 10:35, Stéphane Letz wrote:
Le 18 avr. 2011 à 08:47, David Henningsson a écrit :
Hi Graham,
I don't want to push the problem back and forward, but in this case I think
it's reasonable to say that:
1) We need to be told by the Jack devs about recommended way to link to the
jac
> Anyway, if we conclude dynamic linking is the way forward, it is reasonable
> to think that there should be a version of JackWeakAPI.cpp that is in C and
> not C++ (just like the rest of FS). I don't exactly know how difficult it
> would be to bring C++ code into FS on all platforms,
OK, Jac
Hi Stéphane,
The 'issue' is that the GPL requires that you are able to distribute
the sourcecode with the binary, and the Stienberg ASIO SDK requires
that you don't distribute the sourcecode. So you (if you're the only
author of the JackRouter code) can state a license exception (like the
LinuxSam
Le 18 avr. 2011 à 08:47, David Henningsson a écrit :
> Hi Graham,
>
> I don't want to push the problem back and forward, but in this case I think
> it's reasonable to say that:
>
> 1) We need to be told by the Jack devs about recommended way to link to the
> jack headers.
> Does that means dy
