ADHOC/replicant-vendor_replicant
3
0
Fork 0
Code Issues 6 Pull Requests Releases Activity
11d5cdb86f
replicant-vendor_replicant/products/cyanogen_z71.mk

32 lines
1.1 KiB
Makefile
Raw Normal View History

Z71: Add Commtiva Z71 product Yay, 13 devices (so far), 1 product. Change-Id: Ie2e84525c93dfff3da3d271066d714956c185a16
2010-11-04 15:04:45 +00:00
# Inherit AOSP device configuration for z71.
$(call inherit-product, device/commtiva/z71/device_z71.mk)
# Inherit some common cyanogenmod stuff.
Split up common.mk for smaller devices Capable devices now inherit from common_full.mk, where smaller devices can inherit from common.mk. This currently excludes the extra ringtones and built in themes. Change-Id: I604ac29648a7311ba1dcc9a8005b1be1424ce596
2011-01-22 07:53:32 +00:00
$(call inherit-product, vendor/cyanogen/products/common_full.mk)
Z71: Add Commtiva Z71 product Yay, 13 devices (so far), 1 product. Change-Id: Ie2e84525c93dfff3da3d271066d714956c185a16
2010-11-04 15:04:45 +00:00
# Include GSM stuff
$(call inherit-product, vendor/cyanogen/products/gsm.mk)
#
# Setup device specific product configuration.
#
PRODUCT_NAME := cyanogen_z71
PRODUCT_BRAND := commtiva
PRODUCT_DEVICE := z71
PRODUCT_MODEL := Z71
PRODUCT_MANUFACTURER := Commtiva
vendor: Externalize common version and release names We have been using a system where each vendor makefile needed to be updated for each release. This leads to both redundancy and inconsistency across devices. This patch externalizes version code to the common_versions.mk. As we all know CyanogenMod versioning works as such: MAJOR.MINOR.MAINTENACE.DEVICE_SPECIFIC (i.e. 7.1.0.1) common_versions.mk now contains the first three in the form of the following variables: PRODUCT_VERSION_MAJOR, PRODUCT_VERSION_MINOR, PRODUCT_VERSION_MAINTENANCE. Additionally, each device makefile contains two additional flags which control both the release name (the name that appears in the generated zip) and the device-specific version (empty by default, to be bumped on a per device basis), example: PRODUCT_RELEASE_NAME := XperiaArc-LT15i PRODUCT_VERSION_DEVICE_SPECIFIC := .1 Change-Id: I15d18e27b89ea00109a61cb66e3bffbb061a2ed4
2011-10-13 16:39:00 +00:00
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=commtiva_z71 BUILD_ID=GRJ22 BUILD_FINGERPRINT=google/passion/passion:2.3.4/GRJ22/121341:user/release-keys PRIVATE_BUILD_DESC="passion-user 2.3.4 GRJ22 121341 release-keys"
Z71: Add Commtiva Z71 product Yay, 13 devices (so far), 1 product. Change-Id: Ie2e84525c93dfff3da3d271066d714956c185a16
2010-11-04 15:04:45 +00:00
#PRODUCT_SPECIFIC_DEFINES += TARGET_PRELINKER_MAP=$(TOP)/vendor/cyanogen/prelink-linux-arm-z71.map
vendor: Externalize common version and release names We have been using a system where each vendor makefile needed to be updated for each release. This leads to both redundancy and inconsistency across devices. This patch externalizes version code to the common_versions.mk. As we all know CyanogenMod versioning works as such: MAJOR.MINOR.MAINTENACE.DEVICE_SPECIFIC (i.e. 7.1.0.1) common_versions.mk now contains the first three in the form of the following variables: PRODUCT_VERSION_MAJOR, PRODUCT_VERSION_MINOR, PRODUCT_VERSION_MAINTENANCE. Additionally, each device makefile contains two additional flags which control both the release name (the name that appears in the generated zip) and the device-specific version (empty by default, to be bumped on a per device basis), example: PRODUCT_RELEASE_NAME := XperiaArc-LT15i PRODUCT_VERSION_DEVICE_SPECIFIC := .1 Change-Id: I15d18e27b89ea00109a61cb66e3bffbb061a2ed4
2011-10-13 16:39:00 +00:00
# Release name and versioning
PRODUCT_RELEASE_NAME := Z71
PRODUCT_VERSION_DEVICE_SPECIFIC :=
-include vendor/cyanogen/products/common_versions.mk
Z71: Add Commtiva Z71 product Yay, 13 devices (so far), 1 product. Change-Id: Ie2e84525c93dfff3da3d271066d714956c185a16
2010-11-04 15:04:45 +00:00
#
# Copy legend specific prebuilt files
#
PRODUCT_COPY_FILES += \
vendor/cyanogen/prebuilt/mdpi/media/bootanimation.zip:system/media/bootanimation.zip
Reference in New Issue Copy Permalink