Just to make it clear, the x86 Android port, at that point, requires running an Android kernel on a x86 device with flash storage. This is very different from running Dalvik under Windows or a pre-existing Linux installation (though with time these things will be possible to)
On Sun, Nov 9, 2008 at 10:01 AM, DYChen <[EMAIL PROTECTED]> wrote: > > > > On Nov 7, 6:42 pm, Brian Swetland <[EMAIL PROTECTED]> wrote: > > > > The engineer responsible for this project has been out of the office for > > a couple weeks and is travelling this week. He's working with our team > > to get his patches into the open source tree, but I think we're still a > > couple weeks away from completion there. We know people are excited > > about building android for x86 targets and will try to get this code > > cleaned up and submitted soon. > > Brian, > > Thanks for the update. I look forward to the release of x86 patches > that will enable us to run Android natively on x86 devices or PC. > > Do you know how the project repositories will be structured to > accommodate the support of various x86 devices or targets? Are we > going to see different branches for x86 port? Are we expect to see > macros (such as #ifdef X86) guarding x86 related code in the source? > I'm looking for some guidelines on how x86 related code should be > integrated with the existing Android source. I haven't seen any > guideline regarding coding style or repository structures for hosting > device or architecture specific code yet. Maybe I haven't looked hard > enough. Any pointer is greatly appreciated. > > Thanks, > Dong-Yuan > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
