| commit | 8af44a923fd775ea0dbd5036c8a7bf5bf0d75a86 | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Thu Nov 24 18:36:47 2022 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Mon Nov 28 15:01:30 2022 +0900 |
| tree | 05fa3662b5296783356da4b21a3ac219c76b1ddb | |
| parent | f9ff3414818de3804405ad2be0839c1b17ee7da4 [diff] |
Refactor: remove --apex-info-file arg to checkvintf Now, checkvintf finds input file from dirmaps. We don't need to pass around --apex-info-file. dump_apex_info also generates files under /apex without an explicit --out_file argument. This makes "make" know less about coupling between dump_apex_info and checkvintf. Bug: 260310732 Test: manually run check_target_files_vintf -v target-files Change-Id: Ibfe31978e983e13df35c32521913d5cbc89dc1d1
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.