commit | 009d6f8c73fd2519ba1401fb3bea04b517566fc8 | [log] [tgz] |
---|---|---|
author | David Anderson <dvander@google.com> | Fri Nov 12 02:01:29 2021 +0000 |
committer | David Anderson <dvander@google.com> | Tue Nov 30 15:13:56 2021 -0800 |
tree | c806e2ab2b53610cbf291acb948f33d032274cb0 | |
parent | af78df05536aa731eccbd3e67ca242ee164ff88f [diff] |
build_image: Query the actual image size after invoking the final mkfs. It's not guaranteed that the requested image size to mkfs is precisely respected, due to metadata alignment and such. For accurate care maps use the real image size rather than requested. Bug: 205541521 Test: smartsync to 7892270, check that care_map.pb has the right block count Change-Id: I60fe64f720db13d3c3c4f1d8968341d7293217c9
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.