| commit | 149860f2940209a7f662585bc646c99fe14d2d4c | [log] [tgz] |
|---|---|---|
| author | Bill Yang <yangbill@google.com> | Tue Jul 22 23:36:34 2025 +0000 |
| committer | Bill Yang <yangbill@google.com> | Tue Jul 22 17:28:41 2025 -0700 |
| tree | a9afa0b99acde06b815336e8c731f64a56b4ed3f | |
| parent | 5e0763661a1f884c11c0b6050062c5822f0ec991 [diff] |
Align dynamic_partitions_info.txt generation with super.img For super.img generation it will need both PRODUCT_USE_DYNAMIC_PARTITIONS and BOARD_SUPER_PARTITION_SIZE being set but for dynamic_partitions_info.txt is not, align the same logic between both of them. Bug: 432081907 Test: m droid dist Change-Id: Idab85e96b816c88d308b1fa01116cf1e1061ced0
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.