| commit | c33aec868bf914d36fa862bd3450a66805eabe03 | [log] [tgz] |
|---|---|---|
| author | Devin Moore <devinmoore@google.com> | Sat Jul 29 00:21:46 2023 +0000 |
| committer | Devin Moore <devinmoore@google.com> | Mon Jul 31 16:10:59 2023 +0000 |
| tree | 085fbc3883e88bdeb5c1fef51d959cdad99b79f9 | |
| parent | 9997fdbacf90ba6a41a14e1bbc5b499dce7fd669 [diff] |
Let assemble_vintf create the output fragments Instead of checking, then copying the fragments into the out directory, we pass in the output file and let assemble_vintf create the output file. Test: m Bug: 290265210 Change-Id: I65c2ee826de73b805b48dc95f20c2405250587f8
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.