On Fri, Sep 4, 2009 at 1:52 PM, Aaron Boodman<[email protected]> wrote: > Ok, but does it always have the same structure, and is there a naming > convention?
Yes. The top level folder is always named the plugin name + ".plugin", and always has a file Info.plist inside with all of the metadata, names of the shared library/libraries, etc. (and conversely, each shared library can contain multiple bitnesses and architectures in one file). This is how PluginList finds installed NPAPI plugins, for example. > If so, perhaps we could get away with just relying on the > fact that each platform has a different, but self-consistent > convention. That seems reasonable. If we specify the name of the plugin, can't the loader for each OS locate the corresponding library (windows looks for a .DLL, linux looks for a .so, Mac OS X looks for a .plugin bundle, etc.)? This seems more parallel to how the browser locates and loads plugins. > OTOH, we've decided to be explicit elsewhere in the extensions system, > so I guess we should be here too. I guess that depends on what problem we're trying to solve. I'm not entirely clear on that from Matt's message at the start of this thread. --Amanda --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
