On Fri, Sep 4, 2009 at 10:55 AM, Jói<[email protected]> wrote: > At least on Windows, the NPAPI plug-in would be loaded into the Chrome > process, so there would need to be a flag to select between 32-bit and > 64-bit versions of the plug-in if Chrome starts being available as a > native 64-bit process on Windows. Today the situation is that you run > 32-bit Chrome on 64-bit Windows, so it needs 32-bit DLLs.
Couldn't we have 64-bit browser & render processes with a 32-bit plugin process? It seems simpler to examine the DLL and launch the appropriate type of host process rather than hard-coding that into the manifest (this is what we hope to do for Mac OS X once we have a 64-bit build, for example). --Amanda --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
