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

33 lines
1.1 KiB
Makefile
Raw Normal View History

crespo4g Change-Id: I23b733999b33c29fdcfd1779f6c86472d2a94d9f
2011-05-19 01:07:57 +00:00
# Inherit AOSP device configuration for crespo.
$(call inherit-product, device/samsung/crespo4g/full_crespo4g.mk)
# Inherit some common cyanogenmod stuff.
$(call inherit-product, vendor/cyanogen/products/common_full.mk)
#
# Setup device specific product configuration.
#
PRODUCT_NAME := cyanogen_crespo4g
PRODUCT_BRAND := google
PRODUCT_DEVICE := crespo4g
crespo4g dekang cyanogen vendor to better suit the ns4g Change-Id: I9674cf1d33437066dd3d57ed23b9b6a843b5ed23
2011-05-19 04:09:15 +00:00
PRODUCT_MODEL := Nexus S 4G
crespo4g Change-Id: I23b733999b33c29fdcfd1779f6c86472d2a94d9f
2011-05-19 01:07:57 +00:00
PRODUCT_MANUFACTURER := samsung
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=sojus BUILD_ID=GRJ90 BUILD_FINGERPRINT=google/sojus/crespo4g:2.3.5/GRJ90/138666:user/release-keys PRIVATE_BUILD_DESC="sojus-user 2.3.5 GRJ90 138666 release-keys" BUILD_NUMBER=138666
crespo4g Change-Id: I23b733999b33c29fdcfd1779f6c86472d2a94d9f
2011-05-19 01:07:57 +00:00
# Extra Crespo overlay
PRODUCT_PACKAGE_OVERLAYS += vendor/cyanogen/overlay/crespo4g
# Add the Torch app
PRODUCT_PACKAGES += Torch
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 := NS4G
PRODUCT_VERSION_DEVICE_SPECIFIC :=
-include vendor/cyanogen/products/common_versions.mk
crespo4g Change-Id: I23b733999b33c29fdcfd1779f6c86472d2a94d9f
2011-05-19 01:07:57 +00:00
#
# Copy crespo specific prebuilt files
#
PRODUCT_COPY_FILES += \
vendor/cyanogen/prebuilt/hdpi/media/bootanimation.zip:system/media/bootanimation.zip
Reference in New Issue Copy Permalink