[Development] Untangling our platform plugins

Tor Arne Vestbø Tor.arne.Vestbo at qt.io
Fri May 15 14:43:11 CEST 2020

> On 15 May 2020, at 14:28, Maurice Kalinowski <Maurice.Kalinowski at qt.io> wrote:
>> having a significant part of the plugin's implementation (if not most of
>> it) linked into the parent library leads the concept of "plugin" ad absurdum.
>>> Or, in the case of platforms such as macOS where there’s only one
>>> “platform”, the plugin is built directly into QtGui as a static plugin.
>> the logical consequence of the above would be statically linking the plugins
>> on all platforms. or, for that matter, throwing out the pretense of plugins and
>> just make it a regular factory, to the degree it even makes sense at all.
> [Maurice Kalinowski] 
> What about backends like WebGL, VNC etc.
> It is rather beneficial to decide on runtime which backend to use compared to compile time decision. Especially given that you'd need two different builds then for just a "minimal aspect" of the build.

Agreed, and that part stays as is with the proposal in the OP.

Tor Arne 

More information about the Development mailing list