The steps below describe how to configure makefiles for new mobile devices and products running Android.
productsdirectory beneath the company directory you created in step 1.
vendor/<company_name>/products/<first_product_name>.mk, that includes at least the following code:
$(call inherit-product, $(SRC_TARGET_DIR)/product/generic.mk) # # Overrides PRODUCT_NAME := <first_product_name> PRODUCT_DEVICE := <board_name>
productsdirectory, create an
AndroidProducts.mkfile 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 \
<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.
BoardConfig.mkfile in the directory created in the previous step (
# These definitions override the defaults in config/config.make for <board_name> # # TARGET_NO_BOOTLOADER := false # TARGET_HARDWARE_3D := false # TARGET_USE_GENERIC_AUDIO := true
system.propfile in your
# 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
PRODUCT_MAKEFILES := \ $(LOCAL_DIR)/first_product_name.mk \ $(LOCAL_DIR)/second_product_name.mk
Android.mkfile 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. #
$(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
<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
The file tree below illustrates what your own system should look like after completing the steps above.
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:
|PRODUCT_NAME||End-user-visible name for the overall product. Appears in the "About the phone" info.|
|PRODUCT_MODEL||End-user-visible name for the end product|
|PRODUCT_LOCALES||A space-separated list of two-letter language code, two-letter country code pairs that describe several settings for the user, such as the UI language and time, date and currency formatting. The first locale listed in PRODUCT_LOCALES is is used if the locale has never been set before.||
|PRODUCT_PACKAGES||Lists the APKs to install.||
|PRODUCT_DEVICE||Name of the industrial design||
|PRODUCT_MANUFACTURER||Name of the manufacturer||
|PRODUCT_BRAND||The brand (e.g., carrier) the software is customized for, if any|
|PRODUCT_PROPERTY_OVERRIDES||List of property assignments in the format "key=value"|
|PRODUCT_COPY_FILES||List of words like
|PRODUCT_OTA_PUBLIC_KEYS||List of OTA public keys for the product|
|PRODUCT_POLICY||Indicate which policy this product should use|
|PRODUCT_PACKAGE_OVERLAYS||Indicate whether to use default resources or add any product specific overlays||
|PRODUCT_CONTRIBUTORS_FILE||HTML file containing the contributors to the project.|
|PRODUCT_TAGS||list of space-separated words for a given product|
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