[Webkit-unassigned] [Bug 114966] [Qt] QWebKitPlatformPlugin should export available Plugin interfaces

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri May 3 01:20:11 PDT 2013


--- Comment #17 from Simon Hausmann <hausmann at webkit.org>  2013-05-03 01:18:33 PST ---
(In reply to comment #16)
> (In reply to comment #15)
> > (In reply to comment #14)
> > > The problem with exporting symbols is that then they are subject to binary compatibility constraints. The pure interface approach doesn't require that. 
> > 
> > If I understood correctly, as like other Qt plugins(QPA,imageformats,..) qtwebkitplatformplugin is not binary compatible between Qt deliveries. Suppose if I have a qtwebkitplatformplugin plugin which is compiled against 1.0, the same plugin can't be used as is for 2.0. Am I right? That is the case, I agree with u :), but qwebkitplatformplugin.h shouldn't be a part of Qt delivery.
> > 
> > 
> What about exporting & declaring a clear note like "It is not Binary compatible" as like other Qt plugins?(QPA,imageformats,..)

Then you still get crashes when QtWebKit tries to load a platform plugin that was compiled against the wrong version of the interface.

The crash is what the interface cast and versioning is supposed to protect us against.

If we're willing to give that up, then we could export symbols and actual base classes.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list