blob: c20e8d1284abe2ff31ce6e3cc945ec4fc45dd0fa [file] [log] [blame]
Adnan Begovicf3610f52016-03-15 14:17:47 -07001# Permissions for cmsdk services
2PRODUCT_COPY_FILES += \
3 vendor/cm/config/permissions/org.cyanogenmod.theme.xml:system/etc/permissions/org.cyanogenmod.theme.xml \
Adnan Begovic14768c42016-03-15 14:20:37 -07004 vendor/cm/config/permissions/org.cyanogenmod.livelockscreen.xml:system/etc/permissions/org.cyanogenmod.livelockscreen.xml \
5 vendor/cm/config/permissions/org.cyanogenmod.statusbar.xml:system/etc/permissions/org.cyanogenmod.statusbar.xml
Adnan Begovicf3610f52016-03-15 14:17:47 -07006
7# CM Platform Library
8PRODUCT_PACKAGES += \
9 org.cyanogenmod.platform-res \
10 org.cyanogenmod.platform \
11 org.cyanogenmod.platform.xml
12
13# CM Hardware Abstraction Framework
14PRODUCT_PACKAGES += \
15 org.cyanogenmod.hardware \
16 org.cyanogenmod.hardware.xml
17
18ifndef CM_PLATFORM_SDK_VERSION
19 # This is the canonical definition of the SDK version, which defines
20 # the set of APIs and functionality available in the platform. It
21 # is a single integer that increases monotonically as updates to
22 # the SDK are released. It should only be incremented when the APIs for
23 # the new release are frozen (so that developers don't write apps against
24 # intermediate builds).
25 CM_PLATFORM_SDK_VERSION := 5
26endif
27
28ifndef CM_PLATFORM_REV
29 # For internal SDK revisions that are hotfixed/patched
30 # Reset after each CM_PLATFORM_SDK_VERSION release
31 # If you are doing a release and this is NOT 0, you are almost certainly doing it wrong
32 CM_PLATFORM_REV := 0
33endif
34
35# CyanogenMod Platform SDK Version
36PRODUCT_PROPERTY_OVERRIDES += \
37 ro.cm.build.version.plat.sdk=$(CM_PLATFORM_SDK_VERSION)
38
39# CyanogenMod Platform Internal
40PRODUCT_PROPERTY_OVERRIDES += \
41 ro.cm.build.version.plat.rev=$(CM_PLATFORM_REV)
42