ADHOC/replicant-vendor_replicant
3
0
Fork 0
Code Issues 6 Pull Requests Releases Activity
0051ed6602
replicant-vendor_replicant/config/common_versions.mk

22 lines
824 B
Makefile
Raw Normal View History

CM9: initial CM vendor setup for Android 4
2011-11-27 19:56:54 +00:00
PRODUCT_BRAND := cm
cm: Update for CM9 All targets except Crespo are disabled. Change-Id: I36a8ca549b846dd07f55e689cf2523f5b1fa710c
2011-11-24 21:54:03 +00:00
PRODUCT_VERSION_MAJOR = 9
PRODUCT_VERSION_MINOR = 0
cm: Bump to 7.2.0-RC0 Change-Id: I19d56107f7684401ea4e91ffda181d762bf8112a
2011-11-14 05:29:10 +00:00
PRODUCT_VERSION_MAINTENANCE = 0-RC0
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
cm: Update for CM9 All targets except Crespo are disabled. Change-Id: I36a8ca549b846dd07f55e689cf2523f5b1fa710c
2011-11-24 21:54:03 +00:00
PRODUCT_BUILD_PROP_OVERRIDES += BUILD_DISPLAY_ID=ITL41D
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
CM9: initial CM vendor setup for Android 4
2011-11-27 19:56:54 +00:00
ifdef CM_NIGHTLY
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_PROPERTY_OVERRIDES += \
ro.modversion=CyanogenMod-$(PRODUCT_VERSION_MAJOR)-$(shell date +%m%d%Y)-NIGHTLY-$(PRODUCT_RELEASE_NAME)
else
CM9: initial CM vendor setup for Android 4
2011-11-27 19:56:54 +00:00
ifdef CM_RELEASE
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_PROPERTY_OVERRIDES += \
ro.modversion=CyanogenMod-$(PRODUCT_VERSION_MAJOR).$(PRODUCT_VERSION_MINOR).$(PRODUCT_VERSION_MAINTENANCE)$(PRODUCT_VERSION_DEVICE_SPECIFIC)-$(PRODUCT_RELEASE_NAME)
else
PRODUCT_PROPERTY_OVERRIDES += \
ro.modversion=CyanogenMod-$(PRODUCT_VERSION_MAJOR).$(PRODUCT_VERSION_MINOR).$(PRODUCT_VERSION_MAINTENANCE)$(PRODUCT_VERSION_DEVICE_SPECIFIC)-$(PRODUCT_RELEASE_NAME)-KANG
endif
endif
Reference in New Issue Copy Permalink