Allows to use device-specific EVS configurations

As video and display devices can be named differently on target devices,
EVS configuration files inevitably contain device-specific information.
This change allows a target device to place its own EVS reference
application configuration and EVS reference HAL configuration to
override their defaults.

Bug: 178443960
Test: m -j evs_app android.hardware.automotive.evs@1.1-sample
Change-Id: Ic7b2f6006ad5ac894fb53efc793e1a673a282f36
Merged-In: Ic7b2f6006ad5ac894fb53efc793e1a673a282f36
(cherry picked from commit 263218f0f1a9b6a3708d7d8c215f5e813b0c0cd5)
8 files changed
tree: 937ea248d664f101b41545430c2b0a5922739746
  1. car-bugreportd/
  2. car-default-input-service/
  3. car-internal-lib/
  4. car-lib/
  5. car-maps-placeholder/
  6. car-systemtest-lib/
  7. car-test-lib/
  8. car-usb-handler/
  9. car_product/
  10. computepipe/
  11. cpp/
  12. EncryptionRunner/
  13. evs/
  14. experimental/
  15. FrameworkPackageStubs/
  16. obd2-lib/
  17. packages/
  18. procfs-inspector/
  19. service/
  20. tests/
  21. tools/
  22. user/
  23. vehicle-hal-support-lib/
  24. watchdog/
  25. .clang-format
  26. .gitignore
  27. Android.mk
  28. CleanSpec.mk
  29. CPPLINT.cfg
  30. OWNERS
  31. PREUPLOAD.cfg
  32. README.md
  33. TEST_MAPPING
README.md

Native (C++) code format is required to be compatible with .clang-format file. Run

git clang-format --style=file --extension='h,cpp,cc' HEAD~

Note that clang-format is not desirable for Android java files. Therefore the command line above is limited to specific extensions.