ADHOC/replicant-vendor_replicant
3
0
Fork 0
Code Issues 6 Pull Requests Releases Activity
e87e0c09f7
replicant-vendor_replicant/products/cyanogen_shadow.mk

30 lines
1.2 KiB
Makefile
Raw Normal View History

add cyanogen_shadow product Change-Id: I7173b1288b4c00a70ddc874f8281d4a0c2706ca1
2011-06-12 19:35:56 +00:00
# Inherit AOSP device configuration for passion.
$(call inherit-product, device/motorola/shadow/shadow.mk)
# Inherit some common cyanogenmod stuff.
$(call inherit-product, vendor/cyanogen/products/common_full.mk)
#
# Setup device specific product configuration.
#
PRODUCT_NAME := cyanogen_shadow
PRODUCT_BRAND := motorola
PRODUCT_DEVICE := shadow
PRODUCT_MODEL := DROIDX
PRODUCT_MANUFACTURER := Motorola
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 := DROIDX
PRODUCT_VERSION_DEVICE_SPECIFIC :=
-include vendor/cyanogen/products/common_versions.mk
add cyanogen_shadow product Change-Id: I7173b1288b4c00a70ddc874f8281d4a0c2706ca1
2011-06-12 19:35:56 +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
PRODUCT_BUILD_PROP_OVERRIDES := BUILD_ID=VZW PRODUCT_NAME=shadow_vzw TARGET_DEVICE=cdma_shadow BUILD_FINGERPRINT=verizon/shadow_vzw/cdma_shadow/shadow:2.2.1/VZW/23.340:user/ota-rel-keys,release-keys PRODUCT_BRAND=verizon PRIVATE_BUILD_DESC="cdma_shadow-user 2.2.1 VZW 2.3.340 ota-rel-keys,release-keys" BUILD_NUMBER=2.3.340 BUILD_UTC_DATE=1289194863 TARGET_BUILD_TYPE=user BUILD_VERSION_TAGS=release-keys USER=w30471
add cyanogen_shadow product Change-Id: I7173b1288b4c00a70ddc874f8281d4a0c2706ca1
2011-06-12 19:35:56 +00:00
PRODUCT_COPY_FILES += \
vendor/cyanogen/prebuilt/hdpi/media/bootanimation.zip:system/media/bootanimation.zip
PRODUCT_PACKAGE_OVERLAYS += vendor/cyanogen/overlay/shadow
# Add the Torch app
PRODUCT_PACKAGES += Torch
Reference in New Issue Copy Permalink