| commit | 2e1f5271c5fb7322daeebb28d25d8bfe1057a012 | [log] [tgz] |
|---|---|---|
| author | Håkan Kvist <hakan.kvist@sony.com> | Tue May 11 11:14:48 2021 +0200 |
| committer | Håkan Kvist <hakan.kvist@sony.com> | Tue May 11 16:48:53 2021 +0200 |
| tree | 2b1a76ceeef9119a7fedd0520bf5c539140df2cf | |
| parent | dcadb680112779161077e7d38a78664c2260c4ee [diff] |
When checking if mke2fs is used, compare using basename build_image adds additional parameters (uuid, hash_seed) if prop_dict["ext_mkuserimg"] is set to "mkuserimg_mke2fs". The comparison does not take paths into consideration, so passing a full path to mkuserimg_mke2fs would cause the parameters to not be included. This is currently not an issue for aosp builds, but could cause problems for customized build systems. Bug: 187742822 Test: Manual, using vendor build system, also executed 'm droid' Change-Id: I7a8973dd0c4d8a39aea5aafcfe1aa69750fb1449
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.