Build EVS manager as a part of the car product
This change modifies car_product/build/car_base.mk to build EVS manager
v1.1 by default. To do this, this reorganizes EVS selinux policy files
and places them in each component's directories.
And, this change introduces a new build variable, ENABLE_EVS_SAMPLE.
When this variable is set as true, the reference EVS application and EVS
HAL implementation will be built.
Also, this change replaces a few selinux rules with their equivalent
macros.
Bug: 168017200
Test: Build, flash the image, and manually check audit messages on the
device running in the permissive mode while below executables are
running:
- /system/bin/evs_app
- /system/bin/android.automotive.evs.manager@1.1
- /vendor/bin/android.hardware.automotive.evs@1.1-sample
Change-Id: Ieffabcba6e05e7b20f0282d1346d77e87553fb6a
diff --git a/car_product/build/car_base.mk b/car_product/build/car_base.mk
index 76ec832..9db42b9 100644
--- a/car_product/build/car_base.mk
+++ b/car_product/build/car_base.mk
@@ -65,12 +65,19 @@
PackageInstaller \
car-bugreportd \
-# EVS resources
-PRODUCT_PACKAGES += android.automotive.evs.manager@1.0
-# The following packages, or their vendor specific equivalents should be include in the device.mk
-#PRODUCT_PACKAGES += evs_app
-#PRODUCT_PACKAGES += evs_app_default_resources
-#PRODUCT_PACKAGES += android.hardware.automotive.evs@1.0-service
+# EVS service
+include packages/services/Car/cpp/evs/manager/evsmanager.mk
+
+ifeq ($(ENABLE_EVS_SAMPLE), true)
+# ENABLE_EVS_SAMPLE should set be true or their vendor specific equivalents should be included in
+# the device.mk with the corresponding selinux policies
+PRODUCT_PRODUCT_PROPERTIES += persist.automotive.evs.mode=0
+PRODUCT_PACKAGES += evs_app \
+ android.hardware.automotive.evs@1.1-sample \
+ android.frameworks.automotive.display@1.0-service
+include packages/services/Car/cpp/evs/apps/sepolicy/evsapp.mk
+include packages/services/Car/cpp/evs/sampleDriver/sepolicy/evsdriver.mk
+endif
# Device running Android is a car
PRODUCT_COPY_FILES += \