ADHOC/replicant-vendor_replicant
3
0
Fork 0
Code Issues 6 Pull Requests Releases Activity
131372a7a6
replicant-vendor_replicant/products/cyanogen_click.mk

40 lines
1.3 KiB
Makefile
Raw Normal View History

cm: Add HTC Tattoo Push 4: Created a ldpi structure to share with buzz Push 5: Removed click configs Push 6: Removed windows_media, ril and themes common Change-Id: I697009f86a09d2486a5a49d0f08ca5b60f0efd03
2011-02-01 08:21:12 +00:00
# Inherit AOSP device configuration for click.
$(call inherit-product, device/htc/click/click.mk)
# Inherit some common cyanogenmod stuff.
cm: Add a "common_full_no_themes" makefile for LDPI devices Taken from http://review.cyanogenmod.com/#change,8242 But since it's uncertain if that's ever going to be merged, I though a separate patch for it would be good. Change-Id: Icc5759881d84e10d4d05d371ec600f6fec0017a5
2011-11-01 23:20:57 +00:00
$(call inherit-product, vendor/cyanogen/products/common_full_no_themes.mk)
cm: Add HTC Tattoo Push 4: Created a ldpi structure to share with buzz Push 5: Removed click configs Push 6: Removed windows_media, ril and themes common Change-Id: I697009f86a09d2486a5a49d0f08ca5b60f0efd03
2011-02-01 08:21:12 +00:00
# Include GSM stuff
$(call inherit-product, vendor/cyanogen/products/gsm.mk)
Enable Radio compilation For CLICK Changed fo TI Change-Id: If2b36402537a7b21e43d868680abf17333b5a119
2011-03-06 22:36:36 +00:00
# Broadcom FM radio
$(call inherit-product, vendor/cyanogen/products/ti_fm_radio.mk)
cm: Add HTC Tattoo Push 4: Created a ldpi structure to share with buzz Push 5: Removed click configs Push 6: Removed windows_media, ril and themes common Change-Id: I697009f86a09d2486a5a49d0f08ca5b60f0efd03
2011-02-01 08:21:12 +00:00
# Build kernel
PRODUCT_SPECIFIC_DEFINES += TARGET_PREBUILT_KERNEL=device/htc/click/kernel
#
# Setup device specific product configuration.
#
PRODUCT_NAME := cyanogen_click
PRODUCT_BRAND := htc_wwe
PRODUCT_DEVICE := click
click: Change product model to Tattoo Tattoo is the actual model name, while click is the code name. This is per definitons as in build.prop from original HTC rom. Change-Id: I363634581849bd11b63f77f317dc268568cc4ac5
2011-08-12 22:51:34 +00:00
PRODUCT_MODEL := HTC Tattoo
cm: Add HTC Tattoo Push 4: Created a ldpi structure to share with buzz Push 5: Removed click configs Push 6: Removed windows_media, ril and themes common Change-Id: I697009f86a09d2486a5a49d0f08ca5b60f0efd03
2011-02-01 08:21:12 +00:00
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 += PRODUCT_NAME=htc_click 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"
cm: Add HTC Tattoo Push 4: Created a ldpi structure to share with buzz Push 5: Removed click configs Push 6: Removed windows_media, ril and themes common Change-Id: I697009f86a09d2486a5a49d0f08ca5b60f0efd03
2011-02-01 08:21:12 +00:00
Move ldpi mdpi locales definition to cyanogen_click.mk (arco): Having it here moves them to the end of the PRODUCT_LOCALES list, so it doesn't mess up the default language locale in the rom, making it look like this: http://oi53.tinypic.com/4ttyr5.jpg Change-Id: Ief972c80bfaa237e8f53ad498a5defc8df03778c
2011-04-09 04:54:18 +00:00
# Add LDPI assets, in addition to MDPI
PRODUCT_LOCALES += ldpi mdpi
cm: Add HTC Tattoo Push 4: Created a ldpi structure to share with buzz Push 5: Removed click configs Push 6: Removed windows_media, ril and themes common Change-Id: I697009f86a09d2486a5a49d0f08ca5b60f0efd03
2011-02-01 08:21:12 +00:00
# Extra Passion overlay
PRODUCT_PACKAGE_OVERLAYS += vendor/cyanogen/overlay/ldpi
# Boot animation
PRODUCT_COPY_FILES += \
vendor/cyanogen/prebuilt/ldpi/media/bootanimation.zip:system/media/bootanimation.zip
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 := click
PRODUCT_VERSION_DEVICE_SPECIFIC :=
-include vendor/cyanogen/products/common_versions.mk
Reference in New Issue Copy Permalink