commit | 55e37edf53978492a800a32f223f18feadea6e15 | [log] [tgz] |
---|---|---|
author | Kelvin Zhang <zhangkelvin@google.com> | Tue Feb 18 16:01:25 2025 -0800 |
committer | Kelvin Zhang <zhangkelvin@google.com> | Tue Feb 18 16:04:54 2025 -0800 |
tree | ee0ef3c5ac55df5f8dc4de2e5d1afdfb71b21b48 | |
parent | 3617bc1fc20beaff6de5ed7c272b69e434ec3ef1 [diff] |
Fix dependency issue for boot_ota_16k.zip The dependency list and rule body of build rules are parsed at different stages. This caused a problem, the dependency list is parsed earlier, at which time INSTALLED_BOOTIMAGE_TARGET isn't defined yet. But rule-body is parsed at a later time, when INSTALLED_BOOTIMAGE_TARGET is already defined. This causes non-deterministic build failures, as boot_ota_16k.zip uses boot.img, but didn't list boot.img in dependency list. Build fails if boot.img gets built after boot_ota_16k.zip. To mitigate: 1. Move boot_ota_16k after where INSTALLED_BOOTIMAGE_TARGET is defined 2. Use rule-local variables, this ensures that variables in rule-body are evaluated at the same stage as dependency list. Test: m insatllclean; m boototapackage_16k Bug: 397445008 Change-Id: Ia1f31d093700ea7152a533586bebe1d81f730b27
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.