Detailed Instructions

The steps below describe how to configure makefiles for new mobile devices and products running Android.

1. Create a company directory in //vendor/.
   

     mkdir vendor/<company_name>

2. Create a products directory beneath the company directory you created in step 1.
   

     mkdir vendor/<company_name>/products/

3. Create a product-specific makefile, called vendor/<company_name>/products/<first_product_name>.mk, that includes at least the following code, all values should contain no space:
   

     $(call inherit-product, $(SRC_TARGET_DIR)/product/generic.mk)
       #
       # Overrides
       PRODUCT_NAME := <first_product_name>
       PRODUCT_DEVICE := <board_name>

4. Additional product-specific variables can be added to this Product Definition file.
5. In the products directory, create an AndroidProducts.mk file that point to (and is responsible for finding) the individual product make files.
   

     #
       # This file should set PRODUCT_MAKEFILES to a list of product makefiles
       # to expose to the build system.  LOCAL_DIR will already be set to
       # the directory containing this file.
       #
       # This file may not rely on the value of any variable other than
       # LOCAL_DIR; do not use any conditionals, and do not look up the
       # value of any variable that isn't set in this file or in a file that
       # it includes.
       #
       PRODUCT_MAKEFILES := \
       $(LOCAL_DIR)/first_product_name.mk \

6. Create a board-specific directory beneath your company directory that matches the PRODUCT_DEVICE variable <board_name> referenced in the product-specific make file above. This will include a make file that gets accessed by any product using this board.
   

     mkdir vendor/<company_name>/<board_name>

7. Create a BoardConfig.mk file in the directory created in the previous step (vendor/<company_name>/<board_name>). 
   

     # These definitions override the defaults in config/config.make for <board_name>
       #
       # TARGET_NO_BOOTLOADER := false
       #
       TARGET_USE_GENERIC_AUDIO := true
       TARGET_CPU_ABI := x86

8. If you wish to modify system properties, create a system.prop file in your <board_name>directory(vendor/<company_name>/<board_name>).
   

     # system.prop for 
       # This overrides settings in the products/generic/system.prop file
       #
       # rild.libpath=/system/lib/libreference-ril.so
       # rild.libargs=-d /dev/ttyS0

9. Add a pointer to <second_product_name>.mk within products/AndroidProducts.mk.
   

     PRODUCT_MAKEFILES := \
       $(LOCAL_DIR)/first_product_name.mk \
       $(LOCAL_DIR)/second_product_name.mk

10. An AndroidBoard.mk file must be included in vendor/<company_name>/<board_name> with at least the following code:
    

      # make file for new hardware  from 
        #
        LOCAL_PATH := $(call my-dir)
        #
        # this is here to use the pre-built kernel
        ifeq ($(TARGET_PREBUILT_KERNEL),)
        TARGET_PREBUILT_KERNEL := $(LOCAL_PATH)/kernel
        endif
        #
        file := $(INSTALLED_KERNEL_TARGET)
        ALL_PREBUILT += $(file)
        $(file): $(TARGET_PREBUILT_KERNEL) | $(ACP)
        $(transform-prebuilt-to-target)
        #
        # no boot loader, so we don't need any of that stuff..
        #
        LOCAL_PATH := vendor/<company_name>/<board_name>
        #
        include $(CLEAR_VARS)
        #
        # include more board specific stuff here? Such as Audio parameters.
        #

11. To create a second product for the same board, create a second product-specific make file calledvendor/company_name/products/<second_product_name>.mk that includes:
    

      $(call inherit-product, $(SRC_TARGET_DIR)/product/generic.mk)
        #
        # Overrides
        PRODUCT_NAME := <second_product_name>
        PRODUCT_DEVICE := <board_name>

By now, you should have two new products, called <first_product_name> and <second_product_name> associated with <company_name>. To verify that a product is properly configured (<first_product_name>, for example), execute the following:

  . build/envsetup.sh
make PRODUCT-<first_product_name>-user

You should find new build binaries located in /out/target/product/<board_name>.

New Product File Tree

The file tree below illustrates what your own system should look like after completing the steps above.

• <company_name>
• <board_name>
• AndroidBoard.mk
• BoardConfig.mk
• system.prop
• products
• AndroidProducts.mk
• <first_product_name>.mk
• <second_product_name>.mk

Product Definition Files

Product-specific variables are defined in product definition files. A product definition file can inherit from other product definition files, thus reducing the need to copy and simplifying maintenance.

Variables maintained in a product definition files include:

The snippet below illustrates a typical product definition file.

$(call inherit-product, build/target/product/generic.mk)
#Overrides
PRODUCT_NAME := MyDevice
PRODUCT_MANUFACTURER := acme
PRODUCT_BRAND := acme_us
PRODUCT_LOCALES := en_GB es_ES fr_FR
PRODUCT_PACKAGE_OVERLAYS := vendor/acme/overlay