[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] Which libs really needed for Android

From: Stanislav Kokorev
Subject: Re: [fluid-dev] Which libs really needed for Android
Date: Mon, 12 Oct 2020 15:31:03 +0300

Hi Tom,

Thanks a lot for the detailed explanations!
This sounds even more complex then expected..
And, yep, customization is too much for me.

Tried to use very compact version of libfluidsynth.so extracted from
VolcanoMobile app, but failed.
It almost works, but for some reason there were no audiodrivers.
That was a bit strange because Volcano sources on github are
containing opensles and oboe files.

Thanks a lot !


пн, 12 окт. 2020 г. в 14:30, Tom M. <tom.mbrt@googlemail.com>:
> > why there are so many ".so" files.
> Because fluidsynth itself depends on 3rd party software, most notably
> glib. And this 3rd party software depends on other software. And that
> software depends on software which... ultimately... depends on the
> Android NDK.
> VolcanoMobile has customized fluidsynth, by removing parts of it,
> stripping away functionality, and therefore getting rid of many 3rd
> party software, getting rid of many dependency dependencies. But this
> approach is unmaintainable and thus not supported by upstream
> fluidsynth.
> > Which of the following libs are really needed ?
> All of them, in case you intend to use the prebuilt Android libraries.
> Ofc feel free to cross-compile fluidsynth by yourself, which contains
> only the things you really need. That way, you'd get rid of liboboe.so
> and its dependency libc++_shared.so . This however only applies to
> fluidsynth 2.1.5, because starting from version 2.2.0, C++ will be
> required by fluidsynth. You may be able to get rid of more libs by
> customizing fluidsynth. However, this will be very tricky for someone
> with no experience in C/C++.
> Tom

reply via email to

[Prev in Thread] Current Thread [Next in Thread]