Re: Staying on top of Qt security

[Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>]

Andreas Enge <andreas@enge.fr> writes:

> Hello,
>
> looking at why ardour depends on qt-4, I came across suil:
>     (description
>      "Suil is a lightweight C library for loading and wrapping LV2 plugin UIs.
> Suil makes it possible to load a UI of a toolkit in a host using another
> toolkit.  The API is designed such that hosts do not need to explicitly
> support specific toolkits – if Suil supports a particular toolkit, then UIs in
> that toolkit will work in all hosts that use Suil automatically.
> Suil currently supports every combination of Gtk 2, Qt 4, and X11.")
>
> It is currently used by ardour and jalv, both of which seem to use gtk+-2
> and not qt-4.
>
> The suil package itself, however, depends on gtk+-2 _and_ qt-4.
>
> Do you think we could drop the qt-4 input?
>
> If at some point in time suil also works with qt-5, we might be better
> served by creating two packages, suil-gtk and suil-qt, with only one of
> the respective inputs; I find it unlikely that an application would need
> both of gtk+ and qt.

We cannot know what toolkit the GUI of audio plugins will use.  Suil
supports the three most popular ones so plugin authors providing GUIs
don’t need to worry about support in popular hosts such as Ardour.

~~ Ricardo