| commit | 23a97cd73f21a6204e4e8af09b95a6b356950f07 | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Mon Jul 08 09:17:32 2024 -0700 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Mon Jul 08 09:17:32 2024 -0700 |
| tree | dcca453726f00aaf5961576dac78bad35c0587ca | |
| parent | 1ef79a4dad856fd74a5a722b789c04f8e089a06a [diff] |
Move DTBO target definition outside of BUILDING_RAMDISK_IMAGE guard DTBO taget definition is unintionally moved inside ifdef BUILDING_RAMDISK_IMAGE guard by aosp/3150938 . This causes some targets to miss dtbo building if they don't define a ramdisk. Test: th Bug: 350056336 Change-Id: If840cc57af794b7844593eeed5935f5e10567e3f
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.