| commit | cc00a0cdae3cf2ab2e394754838c89a03a883f41 | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Tue Nov 12 14:04:29 2024 -0800 |
| committer | Cole Faust <colefaust@google.com> | Tue Nov 12 14:19:53 2024 -0800 |
| tree | f203ad05e51f36932519ff8e19f5894ce86f5318 | |
| parent | 4e9d7b3cc1dcfbe4c050b5fd7a6afa792ae07d15 [diff] |
Move write-partition-file-list out of if statement write-partition-file-list was mistakenly moved into an `ifdef BUILDING_RAMDISK_IMAGE`, so it caused other partitions to fail to build on products that don't use a ramdisk. Bug: 378738827 Test: Will run abtd on the failing product Change-Id: I270adbed74054b573e5dab40e5900ceca45e1dfc
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.