| commit | 2d9428e5e97480ec35b1f3ace1a09d1b16be318d | [log] [tgz] |
|---|---|---|
| author | Bill Yang <yangbill@google.com> | Fri Nov 01 03:07:02 2024 +0000 |
| committer | Bill Yang <yangbill@google.com> | Fri Nov 01 07:08:28 2024 +0000 |
| tree | 954ca611f33fe8cea3d3cc8cfc31edadc55ebc0a | |
| parent | 946e129151cc9ba65f3515081e18d5daf711671b [diff] |
Convert vendor_manifest.xml to soong Export DEVICE_MANIFEST_FILE to soong for vendor_manifest convert to soong. Also move vendor_manifest.xml to system/libhidl/vintfdata with other related vintf_data together. Bug: 340427295 Test: m vendor_manifest.xml Change-Id: Idbd0aa05521f65a9d7e6a99dd23f0bfde1b1a5be
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.