0bf940cace
Previously, setting PRODUCT_BUILD_SUPER_PARTITION to false for a partial build (with PRODUCT_USE_DYNAMIC_PARTITIONS == true) would fail to include necessary keys in misc_info.txt that are required when merging two partial builds to create a dynamic-partition-enabled mixed build. This change ensures these necessary keys are included even when PRODUCT_BUILD_SUPER_PARTITION is false. Setting PRODUCT_BUILD_SUPER_PARTITION to false causes partial builds to skip building super.img and super_empty.img, instead relying on these images to come from the final merged build. Bug: 134764140 Test: Building & booting a dynamic-partition-enabled mixed build, and inspecting partial builds' logs / out folder to ensure that super.img/super_empty.img were not created. Change-Id: I99431a9a342e9b0617510e250597f3024ef39322 |
||
|---|---|---|
| common | ||
| core | ||
| packaging | ||
| target | ||
| tests | ||
| tools | ||
| .gitignore | ||
| buildspec.mk.default | ||
| Changes.md | ||
| CleanSpec.mk | ||
| Deprecation.md | ||
| envsetup.sh | ||
| help.sh | ||
| navbar.md | ||
| OWNERS | ||
| README.md | ||
| tapasHelp.sh | ||
| Usage.txt | ||
Android Make Build System
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.