ADHOC/replicant-vendor_replicant
3
0
Fork 0
Code Issues 6 Pull Requests Releases Activity
11d5cdb86f
replicant-vendor_replicant/products/cyanogen_vega.mk

31 lines
985 B
Makefile
Raw Normal View History

Add Advent Vega Change-Id: I52e0f77581d5de7e278c2d51f46b1eb5a30eaae9
2011-03-05 22:22:53 +00:00
$(call inherit-product, device/advent/vega/vega.mk)
# Inherit some common cyanogenmod stuff.
Use common.mk instead of common_full.mk for smaller /system Change-Id: I830a2d431772523de325d51c77d1ca3e46310ba6
2011-05-13 07:06:48 +00:00
$(call inherit-product, vendor/cyanogen/products/common.mk)
Add Advent Vega Change-Id: I52e0f77581d5de7e278c2d51f46b1eb5a30eaae9
2011-03-05 22:22:53 +00:00
#
# Setup device specific product configuration.
#
PRODUCT_NAME := cyanogen_vega
PRODUCT_BRAND := advent
PRODUCT_DEVICE := vega
PRODUCT_MODEL := Vega
PRODUCT_MANUFACTURER := Advent
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=Vega 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" BUILD_NUMBER=121341
Add Advent Vega Change-Id: I52e0f77581d5de7e278c2d51f46b1eb5a30eaae9
2011-03-05 22:22:53 +00:00
# Extra overlay
Vega: Use tablet specific overlays See http://review.cyanogenmod.com/4766 for tablet specific overlay Change-Id: I7f3715620d6549c8bdbcfc5b70f644a528ce1576
2011-04-23 01:21:17 +00:00
PRODUCT_PACKAGE_OVERLAYS += \
vendor/cyanogen/overlay/tablet \
vendor/cyanogen/overlay/vega
Add Advent Vega Change-Id: I52e0f77581d5de7e278c2d51f46b1eb5a30eaae9
2011-03-05 22:22:53 +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 := Vega
PRODUCT_VERSION_DEVICE_SPECIFIC :=
-include vendor/cyanogen/products/common_versions.mk
Add Advent Vega Change-Id: I52e0f77581d5de7e278c2d51f46b1eb5a30eaae9
2011-03-05 22:22:53 +00:00
#
vega: update fingerprint Change-Id: I8fa266f567cf980ba98be25a19a603bc6a686ebc
2011-05-14 07:41:27 +00:00
# Copy Vega specific prebuilt files
Add Advent Vega Change-Id: I52e0f77581d5de7e278c2d51f46b1eb5a30eaae9
2011-03-05 22:22:53 +00:00
#
PRODUCT_COPY_FILES += \
vendor/cyanogen/prebuilt/mdpi/media/bootanimation.zip:system/media/bootanimation.zip
Reference in New Issue Copy Permalink