On Tue, Nov 10, 2009 at 1:52 PM, Gregory Dardyk grego...@google.com wrote:
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
mmentovai, gregoryd and I met today.
We've decided Option #1 is actually bad.
I'm investigating Option #3 which is likely to be cleaner and seems to meet
everyones needs.
I'll be updating this review to that approach shortly.
-BradN
On Wed, Nov 11, 2009 at 5:48 PM, Marc-Antoine Ruel
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
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
