364c1ccaa5
For non-A/B, you must supply the --system-item-list, --other-item-list, and --system-misc-info-keys parameters approrpriate for merging two partial target files. Additionally, you must supply the --rebuild-recovery option to correctly generate the filesystem config and file contexts. With all of these parameters, the script will generate a merged target files containing the correct recovery files. Also fix the --keep-tmp option to be consistent with the other options. Bug: 122813742 Test: verify that merged target image boots and can perform OTA. Change-Id: I5a942ac0cd9924fec419a686794a2340304594c8 |
||
|---|---|---|
| common | ||
| core | ||
| packaging | ||
| target | ||
| tests | ||
| tools | ||
| .gitignore | ||
| buildspec.mk.default | ||
| Changes.md | ||
| CleanSpec.mk | ||
| 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.