Packaging an NPAPI Plugin for Chrome using FireBreath

2
votes

I'm trying to package a plugin created with FireBreath as a Chrome extension. I've read on Chrome Extensions and NPAPI that the way to do that is to include the files in the manifest like so:

"plugins": [
   { "path": "plugin-windows.dll" },
   { "path": "plugin-linux.so" },
   { "path": "plugin-mac.so" }
]

FireBreath compiles the .dll and Linux .so files just fine, but on OS X I get a .plugin file. How do I get the mac.so out of the .plugin file or is there some other way I should package my plugin for Chrome on OS X?

1
macosgoogle-chromegoogle-chrome-extensionnpapifirebreath

1 Answers

2
votes

Sorry, I made a mistake in that post (updating it). For Mac you place the .plugin file so it should be:

{ "path":  "plugin-mac.plugin" }