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

47 lines
1.7 KiB
Makefile
Raw Normal View History

add droid2we (droid2 global) support (1/2) this is dependant on forking the device tree found here: https://github.com/RevNumbers/android_device_motorola_droid2we Change-Id: Id1e71eef51f310c7bee3320af7d6095a7b3dd09b
2011-08-02 18:48:33 +00:00
# Inherit device configuration for Droid2WE.
$(call inherit-product, device/motorola/droid2we/droid2we.mk)
# Inherit some common cyanogenmod stuff.
$(call inherit-product, vendor/cyanogen/products/common_full.mk)
# Include GSM stuff
#$(call inherit-product, vendor/cyanogen/products/gsm.mk)
#
# Setup device specific product configuration.
#
PRODUCT_NAME := cyanogen_droid2we
PRODUCT_BRAND := motorola
PRODUCT_DEVICE := droid2we
PRODUCT_MODEL := DROID2 GLOBAL
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
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=droid2we_vzw BUILD_ID=S273 BUILD_FINGERPRINT=verizon/droid2we_vzw/cdma_droid2we/droid2we:2.2/S273/2.4.330:user/ota-rel-keys,release-keys PRIVATE_BUILD_DESC="cdma_droid2we-user 2.2 S273 2.4.330 ota-rel-keys,release-keys" TARGET_DEVICE=cdma_droid2we PRODUCT_BRAND=verizon BUILD_NUMBER=2.4.330 BUILD_UTC_DATE=1287722464 TARGET_BUILD_TYPE=user BUILD_VERSION_TAGS=release-keys USER=xrpk47
add droid2we (droid2 global) support (1/2) this is dependant on forking the device tree found here: https://github.com/RevNumbers/android_device_motorola_droid2we Change-Id: Id1e71eef51f310c7bee3320af7d6095a7b3dd09b
2011-08-02 18:48:33 +00:00
# Build kernel
#PRODUCT_SPECIFIC_DEFINES += TARGET_PREBUILT_KERNEL=
#PRODUCT_SPECIFIC_DEFINES += TARGET_KERNEL_DIR=kernel-msm
#PRODUCT_SPECIFIC_DEFINES += TARGET_KERNEL_CONFIG=cyanogen_droid2we_defconfig
# Extra Droid2WE overlay
PRODUCT_PACKAGE_OVERLAYS += vendor/cyanogen/overlay/droid2we
# Add the Torch app
PRODUCT_PACKAGES += Torch
# Build GanOptimizer
#PRODUCT_PACKAGES += GanOptimizer
# Broadcom FM radio
#$(call inherit-product, vendor/cyanogen/products/bcm_fm_radio.mk)
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 := DROID2WE
PRODUCT_VERSION_DEVICE_SPECIFIC :=
-include vendor/cyanogen/products/common_versions.mk
add droid2we (droid2 global) support (1/2) this is dependant on forking the device tree found here: https://github.com/RevNumbers/android_device_motorola_droid2we Change-Id: Id1e71eef51f310c7bee3320af7d6095a7b3dd09b
2011-08-02 18:48:33 +00:00
#
# Copy Droid2WE specific prebuilt files
#
PRODUCT_COPY_FILES += \
vendor/cyanogen/prebuilt/hdpi/media/bootanimation.zip:system/media/bootanimation.zip
Reference in New Issue Copy Permalink