| commit | ab09c84c5f0db76b6d830fa9133ac8a07988ae80 | [log] [tgz] |
|---|---|---|
| author | Yi-Yo Chiang <yochiang@google.com> | Thu Feb 22 11:05:43 2024 +0800 |
| committer | Yi-Yo Chiang <yochiang@google.com> | Thu Feb 22 11:47:02 2024 +0000 |
| tree | 4ffaaff8b48b6393f0af96e9988ff243b4389ca2 | |
| parent | 407073150782cc0adfa9042cfe41df5ba45cdb14 [diff] |
core/Makefile: Define write-file-lines unconditionally Right now write-file-lines is defined only if BUILDING_SYSTEM_IMAGE is true. This means split build / partial build targets that doesn't build the system image, would fail to build other partition images too because the $(<parttition>image_intermediates)/file_list.txt build rule would be undefined. Move the macro definition out of the `ifdef BUILDING_SYSTEM_IMAGE` conditional block. Bug: 326359088 Test: build a target that doesn't build system image Change-Id: I020c28f7011bd0df0330ba3350e50bea2b75aab4
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.