[vlc-devel] [PATCH 1/2] bank: enable static modules for mach-o binaries
remi at remlab.net
Fri Mar 6 19:46:11 CET 2020
Le 2020-03-06 19:09, Alexandre Janniaux a écrit :
>> The problem is how to link dynamically loaded plugins if libvlccore is
>> not a
>> shared library, and how we used to do that.
> I agree with you. Currently Android and iOS use static
> libraries and build a single dynamic library from libvlc,
> libvlccore, libcompat, and all static plugins. There is
> currently not out-of-tree plugins usage on Android and iOS
> because it is basically not supported, or half-supported by
> doing your own build of libvlc, which defeats extensibility.
I don't exactly get where you are going with this.
It would have been nice if we had a proper clean common build system for
a static LibVLC. But we don't because it's not really supported by
autotools. And it would seem like a waste of time to make one up in the
current build system.
If that's what rocks your boat, there's no shortage of module subsystem
enhancements or cleanups that would affect the code rather than the
build system in the mean time.
But in any case, I don't think third party vendors would use VLC's
LibVLC on mobile platforms, like they might do on desktop. As such, the
issue of supporting static and dynamic plugins simultaneously seems kind
of irrelevant on mobile.
More information about the vlc-devel