platform_build/target/board/vbox_x86
Jean-Baptiste Queru 8f8624e61f am 9caacbd7: am 5ea72eff: Use the new location of the emulator kernel
* commit '9caacbd74328624dfc753cecfc42cb29bf14bfad':
  Use the new location of the emulator kernel
2012-01-06 17:41:07 -08:00
..
AndroidBoard.mk Fix build scripts for vbox_x86 target 2011-04-01 08:24:25 -07:00
BoardConfig.mk Fix ADB, and a typo in BoardConfig.mk 2011-04-05 17:28:43 -07:00
device.mk am 9caacbd7: am 5ea72eff: Use the new location of the emulator kernel 2012-01-06 17:41:07 -08:00
disk_layout.conf x86: Add in the VirtualBox emulator as a separate build target 2011-03-01 13:04:21 -08:00
init.rc x86: Add in the VirtualBox emulator as a separate build target 2011-03-01 13:04:21 -08:00
init.vbox_x86.rc Fix ADB, and a typo in BoardConfig.mk 2011-04-05 17:28:43 -07:00
README.txt x86: Add in the VirtualBox emulator as a separate build target 2011-03-01 13:04:21 -08:00
system.prop x86: Add in the VirtualBox emulator as a separate build target 2011-03-01 13:04:21 -08:00

The "vbox_x86" product defines a non-hardware-specific target intended
to run on the VirtualBox emulator.

Most of the Android devices (networking, phones, sound, etc) do not work.

ADB via ethernet works with this target. You can use 'adb install' to
test applications that do not require network, phone or sound support.
This emulation is useful because VirtualBox runs much faster then does the
QEMU emulators (at least until a KVM enabled QEMU emulator is available).