[Qt-interest] Qt application as browser plugin ?

Frank Hemer frank at hemer.org
Wed Mar 10 23:47:17 CET 2010


On Wednesday 10 March 2010 23:01:04 Martin Schröer wrote:
> Francesco Tamagni schrieb:
> > On Wed, Mar 10, 2010 at 8:43 PM, Steven Doerfler <sgd-qt at lugaru.com> 
wrote:
> >> But which DLL you get depends on the PATH environment variable, among
> >> other things.  How do you know it's set the same when your DLL is called
> >> from the browser as it is in depwalker's environment?
> >
> > Steven is right...
> >
> > how do you deploy your plugin to make it visible to firefox?
> >
> >
> > if you put your plugin dll and all dependency dlls in a directory
> > (e.g. subdir of program files) and set a registry entry to point there
> > as described in "First install problem" you are quite sure that the
> > right dlls are the ones loaded.
> >
> > see :
> >
> > https://developer.mozilla.org/en/Plugins/The_First_Install_Problem
> >
> >
> > f.
> >
> > _______________________________________________
> > Qt-interest mailing list
> > Qt-interest at trolltech.com
> > http://lists.trolltech.com/mailman/listinfo/qt-interest
>
> Tried that, copied the app.dll and QtCore4.dll to a designated folder.
> Created registry entry under HKEY_LOCAL_MACHINE\Software\MozillaPlugins\
> as suggested by the link provided, added information about the plugin,
> especially the
> path.
>
> Firefox still not showing up anything, Chrome still complaining about
> missing procedure entry point.

... there was a chrome qt port ... if so, you could verify your plugin does 
not use some qt libs used by chrome (and that are probably of a different 
version).

Easiest way will be to first try with the examples that come with 
qtbrowserplugin ... if you have same problems, its time to verify your 
environment.

Frank




More information about the Qt-interest-old mailing list