Am Montag, 23. Juli 2018 21:52 CEST, "Nick Heyworth"
schrieb:
> So you have an unofficial port of glib that can be used to build FluidSynth
> so it runs on Android?
>
> Any chance you can share the binaries (I’m hopeless at building Linux stuff
> using the command line, only know how to b
So you have an unofficial port of glib that can be used to build FluidSynth so
it runs on Android?
Any chance you can share the binaries (I’m hopeless at building Linux stuff
using the command line, only know how to build Android apps) and a simple
example?
All I want to do is load an arbitrar
Thanks Tom, I have copied your changes into the code file.
On 7/23/18, Tom M. wrote:
> fluid_synth_activate_octave_tuning(context->synth, jtuningBank,
> jtuningProgram, name, derivations, 0);
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://list
It should be
fluid_synth_activate_octave_tuning(context->synth, jtuningBank,
jtuningProgram, name, derivations, FALSE);
i.e. no quotes around FALSE and (char*) cast intentionally removed.
FALSE is usually defined as macro which expands to 0 during
compilation. Thus, if the above line doesnt compi
On 7/23/18, Tom M. wrote:
> I am absolutely convinced that upstream fluidsynth can be compiled for
> Android. All you have to do is to cross compile glib and then carry on
> cross compiling fluidsynth.
http://zwyuan.github.io/2016/07/17/cross-compile-glib-for-android/
___
Awesome list, thanks!
I replaced
fluid_synth_create_octave_tuning(context->synth, jtuningBank,
jtuningProgram, (char*)name, derivations);
with
fluid_synth_activate_octave_tuning(context->synth, jtuningBank,
jtuningProgram, (char*)name, derivations, "FALSE");
And it now compiles. Will get to testi
I am absolutely convinced that upstream fluidsynth can be compiled for
Android. All you have to do is to cross compile glib and then carry on
cross compiling fluidsynth. This surely is an exhausting full time day
job, but I dont see a barrier that keeps you from doing so.
So, I'm afraid we are muc
Thanks, I'll take a look at the list and see if I can edit
fluidsynthJNI.c to match
On 7/23/18, Tom M. wrote:
> The idea of a major version bump (1.1 -> 2.0) is to cleanup APIs. This
> has been done and therefore you are expected to run into build
> failures when still using the old 1.1.x API.
>
The idea of a major version bump (1.1 -> 2.0) is to cleanup APIs. This
has been done and therefore you are expected to run into build
failures when still using the old 1.1.x API.
You (or some programmer) must adapt the fluidsynthJNI.c to the new 2.0
API in order to successfully compile. Almost all
So do I, but this is not going to happens... like ever.
The issue can be summarised to "get rid of glib dependancy".
glib is used as portable layer for alot of FluidSynth internals,
unfortunately glib has no Android port...
So we are stuck with unofficial forks like mine...
I try to keep it update
10 matches
Mail list logo
