Windows plugin works with FF on trunk, but not FF released
Mike C
This is my first post to this list.
I have an FF on Windows plugin that works in both 3.x and 5.x. I have a
dual build config.
The 5.x plugin will load and work fine from the FF source I pulled down an
built myself, but it won't load and work with the standard FF 5.x release.
I initially pulled down the entire FF source tree to debug why my plugin was
not loading, only to find that with my home built source, the plugin does
load. So I'm still stuck.
about:plugins shows my plugin, but I assume that's only because the code for
about:plugins just looks at the version info.
When using FF 5.x release, my plugin DLL never gets loaded when the MIME
type for my plugin is parsed, therefore NP_Initialize never gets called.
But, like I stated, when I open the same HTML page in FF 5.x debug, my
plugin DLL is loaded and NP_Initialize is called.
Anyone else ever run into this?
Thanks,
Mike
Benjamin Smedberg
> Hi All,
>
> This is my first post to this list.
>
> I have an FF on Windows plugin that works in both 3.x and 5.x. I have a
> dual build config.
>
> The 5.x plugin will load and work fine from the FF source I pulled down an
> built myself, but it won't load and work with the standard FF 5.x release.
or symbol which is not present in a release version. Are you linking
against any Mozilla library (you shouldn't be). What version of the C
runtime library are you using (you should probably be using the
statically linked version).
You can use the dynamic mode of dependency walker to view any of these
sorts of errors: http://www.dependencywalker.com/
> about:plugins shows my plugin, but I assume that's only because the code for
> about:plugins just looks at the version info.
That is probably correct.
--BDS
