1# List of apps and optional libraries (Java and native) to put in the add-on system image. 2PRODUCT_PACKAGES := \ 3 PlatformLibraryClient \ 4 com.example.android.platform_library \ 5 libplatform_library_jni 6 7# Manually copy the optional library XML files in the system image. 8PRODUCT_COPY_FILES := \ 9 device/sample/frameworks/PlatformLibrary/com.example.android.platform_library.xml:system/etc/permissions/com.example.android.platform_library.xml 10 11# name of the add-on 12PRODUCT_SDK_ADDON_NAME := platform_library 13 14# Copy the manifest and hardware files for the SDK add-on. 15# The content of those files is manually created for now. 16PRODUCT_SDK_ADDON_COPY_FILES := \ 17 device/sample/sdk_addon/manifest.ini:manifest.ini \ 18 device/sample/sdk_addon/hardware.ini:hardware.ini \ 19 $(call find-copy-subdir-files,*,device/sample/skins/WVGAMedDpi,skins/WVGAMedDpi) 20 21 22# Add this to PRODUCT_SDK_ADDON_COPY_FILES to copy the files for an 23# emulator skin (or for samples) 24#$(call find-copy-subdir-files,*,device/sample/skins/WVGAMedDpi,skins/WVGAMedDpi) 25 26# Copy the jar files for the optional libraries that are exposed as APIs. 27PRODUCT_SDK_ADDON_COPY_MODULES := \ 28 com.example.android.platform_library:libs/platform_library.jar 29 30# Rules for public APIs 31PRODUCT_SDK_ADDON_STUB_DEFS := $(LOCAL_PATH)/addon_stub_defs 32 33# Name of the doc to generate and put in the add-on. This must match the name defined 34# in the optional library with the tag 35# LOCAL_MODULE:= platform_library 36# in the documentation section. 37PRODUCT_SDK_ADDON_DOC_MODULES := platform_library 38 39# This add-on extends the default sdk product. 40$(call inherit-product, $(SRC_TARGET_DIR)/product/sdk.mk) 41 42# Real name of the add-on. This is the name used to build the add-on. 43# Use 'lunch <PRODUCT_NAME>-userdebug; m sdk_addon' to build the add-on. 44PRODUCT_NAME := sample_addon 45