commit | b92b8f48fc5facfad99177c878abed9abf379799 | [log] [tgz] |
---|---|---|
author | Jiyong Park <jiyong@google.com> | Mon Mar 15 23:13:42 2021 +0900 |
committer | Jiyong Park <jiyong@google.com> | Wed Mar 17 16:28:16 2021 +0900 |
tree | a2235b90046b8ca3d1b0c067adf535f6ebbea4d3 | |
parent | 82a4cfb397190fa7f1182692891e4532b9fda22f [diff] |
verity_utils.py is a standalone binary verity_utils.py gets an entry point and becomes a host binary. This is to support signing images from the "bootimg" module type. Previously this was done by directly invoking "avbtool" from the soong module, but that required people to know the partition_size priori. The partition size may not be known before actually building the partition image especially when the partition is not for a physical partition but for a partition in a composite image. verity_utils.py, when the partition_size is not given, is capable of calculating the mininum required partition size based on the size of the unsigned input image file. Bug: 180676957 Test: m microdroid_boot-5.10 Change-Id: I7bef292fb141c90899b7bdc0748895f95f964829
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.