commit | 078bfdfeb42a135e23efea64f45e452340a210e5 | [log] [tgz] |
---|---|---|
author | Devin Moore <devinmoore@google.com> | Thu Jun 01 17:54:03 2023 +0000 |
committer | Devin Moore <devinmoore@google.com> | Mon Jun 26 18:01:03 2023 +0000 |
tree | 04067d5b12bc40d51b062a4d02d85a065b532d75 | |
parent | a3b0027fdbc4d623f5ea4f881fa0eae64ddc6d32 [diff] |
Pass system_ext and product dirs to libvintf Now that we have manifest fragements in system_ext, we need to tell libvintf about them. Test: lunch aosp_bramble-userdebug && m Bug: 218588089 Change-Id: Iae56d3b8c790fa1d12321f8c3446a04a0ea816d5
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.