On Aug 27, 6:49 pm, Dianne Hackborn <hack...@android.com> wrote: > Trying to get a somewhat realistic environment running natively on a desktop > is thus tricky enough if that desktop is Linux; it has actually been a very > long time since the simulator did anything besides run all of the > applications as threads inside of a single process, which is extremely > different than the real environment. Someone could maybe cobble this > together to work on Linux again (requiring you to install a desktop build of > the binder driver etc), but it's really difficult to maintain even the > single process version. Trying to get this running on something like > Windows would be a long long rough road.
Ah, so it has been tried and found ugly. Running an x86 build in a VM should work though (to the degree the x86 builds work), and should be substantially faster then emulating an arm chip, right? I do think emulating the processor was the right choice for the official sdk emulator (vs the pre sdk's x86 VM approach), but the VM approach does seem like it would be a great unofficial tool for speeding up less accuracy-critical work. Or we could go the other way... instead of trying to graft android onto a desktop linux, we could try to graft enough of a desktop linux userland onto an x86 android netbook to run eclipse and gcc and have ourselves a hosted development playground... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
