On Fri, Sep 4, 2009 at 10:50 AM, Amanda Walker<[email protected]> wrote: > On Fri, Sep 4, 2009 at 1:34 PM, Aaron Boodman<[email protected]> wrote: >> Yeah, I am kinda curious whether this approach can work generically >> without adding anything to the manifest. Particularly since there is a >> naming convention for shared libraries on all platforms. > > Plugins aren't even always just shared libraries. A Mac NPAPI plugin > is more than a bare shared library--it's a folder ("bundle") that > contains a shared library and a property list file at a minimum (which > is handy, since it lets us read the metadata for the plugin without > having to map in the library), resources used by the plugin, etc.
Ok, but does it always have the same structure, and is there a naming convention? If so, perhaps we could get away with just relying on the fact that each platform has a different, but self-consistent convention. OTOH, we've decided to be explicit elsewhere in the extensions system, so I guess we should be here too. - a --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
