> > > 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.
Maurice _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
