| commit | 2b72b7f01e446c2f270f24b840f484bd7c339165 | [log] [tgz] |
|---|---|---|
| author | Mark Salyzyn <salyzyn@google.com> | Wed Nov 07 07:40:31 2018 -0800 |
| committer | Mark Salyzyn <salyzyn@google.com> | Wed Nov 07 15:51:32 2018 -0800 |
| tree | 12ee7bb26ff50f9daf57a227d3001128f34d1d07 | |
| parent | 41f781de9e907a22af17fcbd512b6cedf738c335 [diff] |
build: Split out mkfs in BuildImageMkfs Separate out BuildImageMkfs from BuildImage, which just makes the filesystem without any verity, avb, or other decisions. BuildImage does all the wrapping for such. This will hopefully ease maintenance and drop the issues surrounding BuildImage reentrancy. Change right-size estimation path to use BuildImageMkfs, and do so without verity or avb wrappings. Test: build Bug: 111302946 Change-Id: I30e2e2b727f40ecca5164142f34139f5244f6424
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.