where xxx is usually the vendor's name and yyy is the product name. Historically, we used the
You have to define PRODUCT_PACKAGES, PRODUCT_NAME, PRODUCT_DEVICE in it, and call inherit-product to inherit from a product makefile. I suggest to to inherit generic_x86.mk to get all common x86 rules.
set to true if you hope to compile third party apps like ConnectBot, FileManager introduced by Android-x86.
Set to false if you don't want ALSA audio.
If you don't need bluetooth, set it to false.
Set to true if you need tslib to calibrate the touchscreen.
You can customize your cmdline (kernel boot options)
Set to true if you need wifi support
Specify the firmwares to be included in the target. The firmwares are supposed to be already in build/target/board/generic_x86/firmware/.
You may also specify a different directory in LOCAL_FIRMWARES_DIR.
Specify a hook script to be added in the initrd.img. Usually the script should contain a detect_hardware function that will be called by the init script.
Read eeepc_info as an implementation example.
If you want to include some prebuilt apps (apk files), set them to this variable.
Specify a kernel config file for this target. If not set, the default android-x86_defconfig will be used.
Besides the four makefiles, you may also add the file init.yyy.rc to do some initializations for your product
The file will be included automatically if exists,and called by Android init on booting(after executing init.rc).