| commit | afdd7c74bc7f228b63b0bdec61a524060933e7c9 | [log] [tgz] |
|---|---|---|
| author | Devin Moore <devinmoore@google.com> | Mon Dec 13 22:04:08 2021 +0000 |
| committer | Devin Moore <devinmoore@google.com> | Mon Dec 20 20:54:23 2021 +0000 |
| tree | b18fbfcce695694d9c13573427c4568e68a11008 | |
| parent | 380d9e445c016adf384973ffba92a3fefd53f86a [diff] |
Update releasetools for new init_boot.img
This new init_boot.img contains the ramdisk that used to reside in the
boot.img file.
Test: set BOARD_PREBUILT_INIT_BOOT_IMAGE to an external init_boot.img
- Check that "m" pulls in the init_boot.img to
out/target/product/vsoc_x86_64/
- Check that "m dist" adds the init_boot.img to
aosp_cf_x86_64_phone-img-eng.devinmoore.zip
Test: atest --host releasetools_test
Bug: 203698939
Change-Id: If7ef2cf093e5e525529c7c44333c0f40f6ba0764
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.