50509015bf
Gather all BOARD_BOOTCONFIG parameters. Create vendor-bootconfig.img with parameters seperated by newlines. Pass that file to mkbootimg as --vendor_bootconfig to add it to the vendor_boot.img. Test: Add BOARD_BOOTCONFIG parameters in cuttlefish .mk file Check vendor-bootconfig.img for expected output Verify expected vendor_boot.img format with: unpack_bootimg --boot_image vendor_boot.img Test: Update Cuttlefish bootloader to handle the new vendor_boot.img and check /proc/bootconfig for the expexted parameters. Bug: 173815685 Change-Id: Iaa9b71b4bc64375777a5353396e83bb2beb25c47 |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
Android.bp | ||
Changes.md | ||
CleanSpec.mk | ||
Deprecation.md | ||
METADATA | ||
OWNERS | ||
README.md | ||
Usage.txt | ||
buildspec.mk.default | ||
envsetup.sh | ||
help.sh | ||
navbar.md | ||
rbesetup.sh | ||
tapasHelp.sh |
README.md
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.