Still,
If someone wanted to put the work into it, the problem is solvable.

The example to look at is Microsoft's Visual Studio, launching the VS mobile 
device emulators don't use inordinate resources. This capability is likely 
built into VS because when you launch the MS standalone mobile device 
emulators, they're resource hogs, even more so than what we're seeing with the 
Android emulator.

So, hard to say who should be looking at this... Eclipse? Google?

Also, I don't know that it's necessary for the Android emulator to emulate ARM 
hardware, I assume that Android natively should be able to run on x86 as well 
(especially because of its Linux roots)... Developers like ourselves only care 
what is exposed for us to access which means the Android APIs.

So, maybe it does make sense to investigate Android in VMware.

Tony

----- Original Message -----
From: Disconnect <[email protected]>
Sent: Fri, 7/3/2009 8:57am
To: [email protected]
Subject: [android-beginners] Re: VMWare Image of the Android Emulator


VMware emulates X86. Android emulator emulates arm. So.. no. You could
make it worse by emulating a linux system running the android emulator
though, that'd be funny.

On Fri, Jul 3, 2009 at 10:18 AM, MCON Dev<[email protected]> wrote:
> Is it possible to create a vmware image of the emulator ? After all its a
> operating system image after all. If yes, it would prove very fruitful.
> Currently the emulator takes on a lot of processing power of the development
> machine. Making the development really painful experience. The more complex
> the product becomes the more difficult the development.
> Thanks
> Siddharth
> >
>



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to