| commit | fc3387bb0efeac1801bbc6166060199df7a77aa3 | [log] [tgz] |
|---|---|---|
| author | Po Hu <po.hu@mediatek.com> | Wed Mar 29 17:49:49 2023 +0800 |
| committer | Jiyong Park <jiyong@google.com> | Tue May 09 08:38:39 2023 +0000 |
| tree | 5022d31f5ea9f5c5c2971c2618254bc1cd470434 | |
| parent | 5c5e1b1c0cd17cd6dd821db93125a27263343bb7 [diff] |
Support to merge PREBUILT_IMAGES For example, pvmfw.img comes from framework target files package and dtbo.img comes from vendor target files package. Bug: 270241811 Test: merge_target_files Merged-In: If2e6fac5ce3671e3387e801808a195fb7b2c55b5 Change-Id: If2e6fac5ce3671e3387e801808a195fb7b2c55b5 (cherry picked from commit 81c3f4a884a8491a2d0d480e219cb68c9986562d)
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.