Re: GUI toolkit support
jonetsu <[email protected]>
| Newsgroups | gmane.comp.audio.ardour.user |
|---|---|
| Message-ID | <20181116130659.2a150514@mevla> |
On Fri, 16 Nov 2018 17:56:23 +0100 Robin Gareus <[email protected]> wrote: > Say you write a plugin that needs ffmpeg and uses the newer > libswresample2 interface, and another author writes a plugin that uses > the older libswresample1 API. Now you dynamically link both. Just a probably very stupid question. If plugins from a manufacturer are all using the same statically-linked toolkit, then would it be possible for that manufacturer to ship their plugins with a .so of the toolkit for them to use instead of having that toolkit embedded in every single plugin binary ? The install is then two binaries: the plugin and the toolkit. Any further plugins from that manufacturer installed by the user will use (provided good version control and associated use cases) the same .so toolkit. One might say well, in 10 years from now there'll be a-plenty of those .so toolkit files laying around on the drive since there were updates and no-one ever detected and removed the ones that are not used anymore. Cheers. _______________________________________________ Ardour-Users mailing list [email protected] To unsubscribe or change your mailing preferences please visit: http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org