| commit | 0b21e0f1a6a2a7f696342054c01e08bfe7265ba9 | [log] [tgz] |
|---|---|---|
| author | Bill Yang <yangbill@google.com> | Mon Oct 07 09:52:32 2024 +0000 |
| committer | Bill Yang <yangbill@google.com> | Mon Oct 07 10:20:16 2024 +0000 |
| tree | 2da579d6deb6027723de76aec7b406b5dbac6f9c | |
| parent | b9294988b6558a99adfd8a6139d8faf15471b4d3 [diff] |
Export related variables for vintf_data to soong
Export DEVICE_MATRIX_FILE, PRODUCT_MANIFEST_FILES,
DEVICE_FRAMEWORK_MANIFEST_FILE, and SYSTEM_EXT_MANIFEST_FILES to soong.
Also add related logic for hwservicemanager to PRODUCT_MANIFEST_FILES.
Bug: 340427295
Test: m vendor_compatibility_matrix.xml system_manifest.xml \
product_manifest.xml system_ext_manifest.xml
Change-Id: Ib006a4fb7549d61beb6ec3c4c7ae49dec258daca
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.