ADHOC/replicant-vendor_replicant
3
0
Fork 0
Code Issues 6 Pull Requests Releases Activity
395cb3fb55
replicant-vendor_replicant/products/cyanogen_blade.mk

30 lines
985 B
Makefile
Raw Normal View History

Merge ZTE Blade vendor config. The device config should be forked from https://github.com/TomGiordano/android_device_zte_blade Change-Id: If9c6ebdbc361c0e10c5009b8baf9c27343417ac7
2011-02-11 10:44:39 +00:00
# Inherit AOSP device configuration for blade.
$(call inherit-product, device/zte/blade/device_blade.mk)
# Inherit some common cyanogenmod stuff.
$(call inherit-product, vendor/cyanogen/products/common_full.mk)
# Include GSM stuff
$(call inherit-product, vendor/cyanogen/products/gsm.mk)
#
# Setup device specific product configuration.
#
PRODUCT_NAME := cyanogen_blade
PRODUCT_BRAND := zte
PRODUCT_DEVICE := blade
PRODUCT_MODEL := Blade
PRODUCT_MANUFACTURER := ZTE
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=blade 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"
Merge ZTE Blade vendor config. The device config should be forked from https://github.com/TomGiordano/android_device_zte_blade Change-Id: If9c6ebdbc361c0e10c5009b8baf9c27343417ac7
2011-02-11 10:44:39 +00:00
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 := Blade
PRODUCT_VERSION_DEVICE_SPECIFIC :=
-include vendor/cyanogen/products/common_versions.mk
Merge ZTE Blade vendor config. The device config should be forked from https://github.com/TomGiordano/android_device_zte_blade Change-Id: If9c6ebdbc361c0e10c5009b8baf9c27343417ac7
2011-02-11 10:44:39 +00:00
#
# Copy legend specific prebuilt files
#
PRODUCT_COPY_FILES += \
vendor/cyanogen/prebuilt/hdpi/media/bootanimation.zip:system/media/bootanimation.zip
Reference in New Issue Copy Permalink