We might build Chrome for 64-bit Windows in the future, but there are several reasons why we would like to avoid porting all Chrome code to 64-bit Windows now:
- We are now in the process of porting Native Client code that is 64-bit clean on Linux to 64-bit Windows and it requires some effort. - We currently plan to use only a minimal subset of functionality in the 64-bit Windows binary, so we would like to keep that binary as small as possible Greg On Tue, Nov 10, 2009 at 10:41, Evan Martin <e...@chromium.org> wrote: > On Mon, Nov 9, 2009 at 6:38 PM, Bradley Nelson <bradnel...@google.com> > wrote: > > Currently they are porting base + app to 64-bit for windows. > > They only need a limited subset of functionality for nacl, so they have > only > > made some source files 64-bit clean. > > They would like to simply disable the rest for 64-bit (at least for now). > > We are 64-bit clean on Linux; I would expect much of base is shared? > My recollection is it only took Dean (and Joel?) a week or two to get > us the rest of the way to 64-bit clean. > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev