23a929df62
NFC stack is becoming an unbundled apex which embeds the existing NFC APK. Unbundling requires the apex & apk to be signed by non-platform certificates, hence adding new seapp_contexts rule for the NFC stack. The old rule is also left behing to support `-next` config builds where we are still using the platform signed NFC APK. Ignore-AOSP-First: All of the NFC mainline work is only present in internal master. Will cherry-pick this CL once we cherry-pick all its dependencies. Bug: 320583956 Test: Bootup test with signed NFC APK (within NFC apex) Merged-In: I1d4d6370cce558c8dcc0ec73a7ce47c2b5495a33 Change-Id: I1d4d6370cce558c8dcc0ec73a7ce47c2b5495a33
37 lines
1.1 KiB
Text
37 lines
1.1 KiB
Text
#
|
|
# Maps an arbitrary tag [TAGNAME] with the string contents found in
|
|
# TARGET_BUILD_VARIANT. Common convention is to start TAGNAME with an @ and
|
|
# name it after the base file name of the pem file.
|
|
#
|
|
# Each tag (section) then allows one to specify any string found in
|
|
# TARGET_BUILD_VARIANT. Typcially this is user, eng, and userdebug. Another
|
|
# option is to use ALL which will match ANY TARGET_BUILD_VARIANT string.
|
|
#
|
|
|
|
[@PLATFORM]
|
|
ALL : $DEFAULT_SYSTEM_DEV_CERTIFICATE/platform.x509.pem
|
|
|
|
[@SDK_SANDBOX]
|
|
ALL : $MAINLINE_SEPOLICY_DEV_CERTIFICATES/sdk_sandbox.x509.pem
|
|
|
|
[@BLUETOOTH]
|
|
ALL : $MAINLINE_SEPOLICY_DEV_CERTIFICATES/bluetooth.x509.pem
|
|
|
|
[@MEDIA]
|
|
ALL : $DEFAULT_SYSTEM_DEV_CERTIFICATE/media.x509.pem
|
|
|
|
[@NETWORK_STACK]
|
|
ALL : $MAINLINE_SEPOLICY_DEV_CERTIFICATES/networkstack.x509.pem
|
|
|
|
[@NFC]
|
|
ALL : $MAINLINE_SEPOLICY_DEV_CERTIFICATES/nfc.x509.pem
|
|
|
|
[@SHARED]
|
|
ALL : $DEFAULT_SYSTEM_DEV_CERTIFICATE/shared.x509.pem
|
|
|
|
# Example of ALL TARGET_BUILD_VARIANTS
|
|
[@RELEASE]
|
|
ENG : $DEFAULT_SYSTEM_DEV_CERTIFICATE/testkey.x509.pem
|
|
USER : $DEFAULT_SYSTEM_DEV_CERTIFICATE/testkey.x509.pem
|
|
USERDEBUG : $DEFAULT_SYSTEM_DEV_CERTIFICATE/testkey.x509.pem
|
|
|