11d5cdb86f
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
20 lines
810 B
Makefile
20 lines
810 B
Makefile
PRODUCT_VERSION_MAJOR = 7
|
|
PRODUCT_VERSION_MINOR = 1
|
|
PRODUCT_VERSION_MAINTENANCE = 0
|
|
|
|
PRODUCT_BUILD_PROP_OVERRIDES += BUILD_DISPLAY_ID=GWK74
|
|
|
|
ifdef CYANOGEN_NIGHTLY
|
|
PRODUCT_PROPERTY_OVERRIDES += \
|
|
ro.modversion=CyanogenMod-$(PRODUCT_VERSION_MAJOR)-$(shell date +%m%d%Y)-NIGHTLY-$(PRODUCT_RELEASE_NAME)
|
|
else
|
|
ifdef CYANOGEN_RELEASE
|
|
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
|
|
|