Compare Revisions

Shipping a plugin as a Toolkit bundle

Change Revisions

Revision 79669:

Revision 79669 by Sheppy on

Revision 79670:

Revision 79670 by mendicant on

Title:
Shipping a plugin as a Toolkit bundle
Shipping a plugin as a Toolkit bundle
Slug:
Shipping_a_plugin_as_a_Toolkit_bundle
Shipping_a_plugin_as_a_Toolkit_bundle
Tags:
NeedsTechnicalReview, Add-ons, Plugins, NeedsMarkupWork
NeedsTechnicalReview, Add-ons, Plugins, NeedsMarkupWork
Content:

Revision 79669
Revision 79670
n53      Gecko 2.0 {{ geckoRelease("2.0") }} removed support fon53      Gecko 2.0 {{ geckoRelease("2.0") }} removed support fo
>r platform-specific subdirectories. Instead, you need to use mani>r platform-specific subdirectories. Instead, you need to place th
>fest flags, such as the <a href="/en/Chrome_Registration#os" titl>e different plugin libraries into the plugins directory.
>e="en/Chrome Registration#os"><code>OS</code></a>&nbsp;and <a hre 
>f="/en/Chrome_Registration#abi" title="en/Chrome Registration#abi 
>"><code>ABI</code></a> flags, in your <a href="/en/Chrome_Registr 
>ation" title="en/Chrome Registration">chrome manifest</a> to spec 
>ify components that should be loaded for specific platforms. 
t59binary-component components/windows/mycomponent.dll ABI=WINNT_x86t59plugins/
>-msvc 
60binary-component components/mac/mycomponent.dylib ABI=Darwin_x86-60    libplugin.so
>gcc3 
61binary-component components/mac/mycomponent64.dylib ABI=Darwin_x861    libplugin.dylib<br>
>6-64-gcc3 
62binary-component components/linux/mycomponent.so ABI=Linux_x86-gc
>c3 

Back to History