platform_build/target/board/vbox_x86
Vladimir Chtchetkine 0216925157 am 2cbcd24b: Cherry-picked from e6b969f3b in master. Do not merge.
* commit '2cbcd24ba708be5e387b8bf54351f5c2df7abbec':
  Cherry-picked from e6b969f3b in master. Do not merge.
2012-01-10 16:42:47 -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
README.txt x86: Add in the VirtualBox emulator as a separate build target 2011-03-01 13:04:21 -08:00
device.mk am 2cbcd24b: Cherry-picked from e6b969f3b in master. Do not merge. 2012-01-10 16:42:47 -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
system.prop x86: Add in the VirtualBox emulator as a separate build target 2011-03-01 13:04:21 -08:00

README.txt

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).