Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Loading NPAPI plugin with different ABI in Firefox 4.0

6 views
Skip to first unread message

Zbynek Michl

unread,
Dec 30, 2010, 9:31:16 AM12/30/10
to
Hello,

I have FF 4.0b9pre and I'd like to load NPAPI plugin. When I place it
into "myExtension/plugins/npMyPlugin.so" directory, it loads fine.
However, when I place plugin into "myExtension/components/linux/
npMyPlugin.so" (according to https://developer.mozilla.org/en/Shipping_a_plugin_as_a_Toolkit_bundle)
and add "binary-component ... ABI=..." into the chrome.manifest file,
plugin doesn't load.

I can place all different ABI versions into the single "myExtension/
plugins/" directory. That works, but it is quite dirty solution.

Any suggestions?

Thanks,
Zb.

Benjamin Smedberg

unread,
Jan 3, 2011, 8:28:27 AM1/3/11
to
On 12/30/10 9:31 AM, Zbynek Michl wrote:

> I have FF 4.0b9pre and I'd like to load NPAPI plugin. When I place it
> into "myExtension/plugins/npMyPlugin.so" directory, it loads fine.
> However, when I place plugin into "myExtension/components/linux/
> npMyPlugin.so" (according to https://developer.mozilla.org/en/Shipping_a_plugin_as_a_Toolkit_bundle)
> and add "binary-component ... ABI=..." into the chrome.manifest file,
> plugin doesn't load.

Plugins are not binary (XPCOM) components. It doesn't make sense to try and
use binary-component with them.

--BDS

Zbynek Michl

unread,
Jan 5, 2011, 9:31:51 AM1/5/11
to
> Plugins are not binary (XPCOM) components. It doesn't make sense to try and
> use binary-component with them.

Ok, so where should I place different arch versions of the plugin?

Zbynek

0 new messages