platform_build

History

Bruce Beare 4c0115d0b7 generic_x86 builds don't need/use the sparse ext4 format. Change-Id: I62973b131a728c3862be4642e2d49d0fa61555ac Signed-off-by: Bruce Beare <bruce.j.beare@intel.com>		2010-12-28 15:33:27 -08:00
..
AndroidBoard.mk	GB Updates for init.rc and boot command line	2010-12-28 14:48:23 -08:00
BoardConfig.mk	generic_x86 builds don't need/use the sparse ext4 format.	2010-12-28 15:33:27 -08:00
disk_layout.conf	Add support for x86 VirtualBox Emulation	2010-05-05 09:52:09 -07:00
init.rc	GB Updates for init.rc and boot command line	2010-12-28 14:48:23 -08:00
README.txt	Move buildspec vars to BoardConfig.mk	2010-07-12 11:32:37 -07:00

README.txt

The generic_x86 board target provides basic services on very basic
hardware (really for an emulation). To build with generic_x86, you will
need an appropriate kernel for your emulation (or device).

A1. Create a new top level directory and pull the AOSP repository
        mkdir $HOME/AOSP
        cd $HOME/AOSP
        repo init -u git://android.git.kernel.org/platform/manifest.git
        repo sync

A2. Copy in the kernel
        cd $HOME/AOSP
        cp ~/bzImage.your_device $HOME/AOSP/prebuilt/android-x86/kernel/kernel

A3. Build
        cd $HOME/AOSP
        source build/envsetup.sh
        lunch generic_x86-eng
        make -j8

The build will generate some image files whose format may or may not be correct for your
device. You can build an installer image disk for the VirtualBox emulator using the command:

A4. Build a VirtualBox installer image
	cd $HOME/AOSP
        source build/envsetup.sh
        lunch generic_x86-eng
        make -j8 installer_vdi