Please use permalinks.
https://github.com/FluidSynth/fluidsynth/blob/1629f9f9976be6e990994489acceb622bd7386da/src/fluidsynth.c#L693
https://github.com/FluidSynth/fluidsynth/blob/1629f9f9976be6e990994489acceb622bd7386da/src/fluidsynth.c#L738
I think all those #ifdef MACINTOSH or DARWIN macros can
Hello,
I was implementing it, but I noticed a strange thing.
Here:
https://github.com/FluidSynth/fluidsynth/blob/master/src/fluidsynth.c#L693
there is a piece of code that it is not emitted for MACOS.
And here:
https://github.com/FluidSynth/fluidsynth/blob/master/src/fluidsynth.c#L738
for some
> In my opinion, the network support should be a feature, not a requirement and
> FluidSynth is a synthesizer,
Ok then, I dont mind if we make this feature optional. In fact there already is
a WITHOUT_SERVER macro for MacOSX. You could start from there, however this
macro should then be called
Hello,
perhaps an embedded platform, like the one I'm working on, or my unreleased
DJGPP port (DJGPP has been added also to CYGWIN distribution recently).
Or the user may want to have not its compiled library to be able to surf the
network.
It is true that some libraries exist for resolving the a
Are you thinking of any specific platform that doesn't support BSD sockets?
Tom
2017-12-08 0:33 GMT+01:00 Carlo Bramini :
> Hello,
> I was wondering what you would think about disabling network with some macro
> like HAVE_NETWORK_SUPPORT at configure time. In other words, the user could
> sel
Hello,
I was wondering what you would think about disabling network with some macro
like HAVE_NETWORK_SUPPORT at configure time. In other words, the user could
select to disable it or not. Having a shell running through the network could
be an useful feature, but it does not look to me so much c
