Mads Sig Ager wrote: > Urgh, that's annoying. I'm probably way too late to this discussion, > but why isn't it sufficient to generate a chromium-ia32 and a > chromium-x64 xcode project. That seems to be what is done on Linux > where we are building and shipping both 64 bit and 32 bit versions?
The strategy for supporting 32-bit plugins in a 64-bit world is different on the Mac. We’ll be starting the plugin process in 32-bit mode on the Mac. In order to do this, everything needs to be universal (fat). There’s no such thing as nspluginwrapper as is used on Linux. This is the primary engineering hurdle. There are other concerns as well, such as user experience and expectations (they’re different on the Mac, “universal” is the general rule and there’s rarely any 32/64 split or user option) and how to handle auto-update when the entire existing installed base is using a 32-bit application but is probably capable of running the 64-bit one. These are informative but not nearly as compelling as the plugin problem (and its solution). Mark -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
