commit | f282f5521da2c2cdb77ef85852a6244044abecc6 | [log] [tgz] |
---|---|---|
author | Yi-Yo Chiang <yochiang@google.com> | Tue Jan 11 17:19:23 2022 +0800 |
committer | Yi-Yo Chiang <yochiang@google.com> | Tue Jan 11 17:31:16 2022 +0800 |
tree | c598c67421fe88bf9f4728ac31c66bb93dfbc6ba | |
parent | 27a309f62770b25b0bc604e51c3fe10f94dd5197 [diff] |
Add boot*.img to default dist target if PRODUCT_EXPORT_BOOT_IMAGE_TO_DIST Right now if PRODUCT_EXPORT_BOOT_IMAGE_TO_DIST is given, $ m dist bootimage would copy boot*.img to the dist dir. After this change, both $ m dist # droidcore $ m dist bootimage would copy boot*.img to the dist dir, the difference is that the latter builds & copies *only* the boot images. Bug: 212486689 Test: m dist bootimage Test: m dist => boot*.img are copied to dist dir Change-Id: I1c714ce5d75eba93e32078b1ac291a181b05405a
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.