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

32 lines
1.1 KiB
Makefile
Raw Normal View History

add heroc to cyanogen vendor
2010-08-09 02:35:47 +00:00
# Inherit AOSP device configuration for heroc.
$(call inherit-product, device/htc/heroc/heroc.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)
add heroc to cyanogen vendor
2010-08-09 02:35:47 +00:00
#
# Setup device specific product configuration.
#
PRODUCT_NAME := cyanogen_heroc
PRODUCT_BRAND := sprint
PRODUCT_DEVICE := heroc
PRODUCT_MODEL := HERO200
PRODUCT_MANUFACTURER := HTC
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=GRI40 BUILD_FINGERPRINT=google/passion/passion:2.3.3/GRI40/102588:user/release-keys PRIVATE_BUILD_DESC="passion-user 2.3.3 GRI40 102588 release-keys"
add heroc to cyanogen vendor
2010-08-09 02:35:47 +00:00
# Extra overlay for Gallery3D orientation hack
add overlays for heroc
2010-08-24 22:29:16 +00:00
PRODUCT_PACKAGE_OVERLAYS += vendor/cyanogen/overlay/heroc
heroc: add heroc to available meals Change-Id: I43f3882e75d2b63072e91836f13dd45ba0c73f4b
2011-02-10 00:53:55 +00:00
PRODUCT_SPECIFIC_DEFINES += TARGET_PRELINKER_MAP=$(TOP)/vendor/cyanogen/prelink-linux-arm-hero.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 := Heroc
PRODUCT_VERSION_DEVICE_SPECIFIC :=
-include vendor/cyanogen/products/common_versions.mk
add heroc to cyanogen vendor
2010-08-09 02:35:47 +00:00
#
# Copy dream/sapphire specific prebuilt files
#
PRODUCT_COPY_FILES += \
product: move bootanim to mdpi/hdpi prebuilt folder for cleanup, adjust make files
2010-08-09 21:29:24 +00:00
vendor/cyanogen/prebuilt/mdpi/media/bootanimation.zip:system/media/bootanimation.zip
Reference in New Issue Copy Permalink