tequilaOS/platform_build
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
platform_build/target/board/vbox_x86
History
Ying Wang 0650d1503d Add PRODUCT_BOOT_JARS to derive BOOTCLASSPATH 
- BOOTCLASSPATH now is product-configurable;
- No need to maintain the duplicate values in core/dex_preopt.mk.
- clean up some legacy ALL_PREBUILTs.
Bug: 9990214

Change-Id: Ie3953e66d282e335bb7782b0ebd56102c35ec10e
2013-07-24 15:15:55 -07:00
..
AndroidBoard.mk Fix build scripts for vbox_x86 target 2011-04-01 08:24:25 -07:00
BoardConfig.mk Add PRODUCT_BOOT_JARS to derive BOOTCLASSPATH 2013-07-24 15:15:55 -07:00
device.mk Add PRODUCT_BOOT_JARS to derive BOOTCLASSPATH 2013-07-24 15:15:55 -07:00
disk_layout.conf x86: Add in the VirtualBox emulator as a separate build target 2011-03-01 13:04:21 -08:00
init.vbox_x86.rc init.vbox_x86.rc: mount data & cache partitions from /dev/sdb 2012-04-06 11:04:53 -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

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