| commit | 730200ec863b385a7c72ae7d8859109afaf13e0f | [log] [tgz] |
|---|---|---|
| author | Peter Collingbourne <pcc@google.com> | Wed Feb 16 13:32:53 2022 -0800 |
| committer | Peter Collingbourne <pcc@google.com> | Thu Feb 17 14:26:56 2022 -0800 |
| tree | 1d5ec0c25c81be5034a2d37eb723f67050098765 | |
| parent | c3ee009f38b2c8c94f6dc6c5b11e3f8851f22304 [diff] |
Make it possible to avoid specifying boot partition sizes. Virtual platforms may have no boot partition as such, so there is no practical limit on the partition size. Therefore, make it possible to omit the partition size (i.e. by omitting a definition of BOARD_*BOOTIMAGE_PARTITION_SIZE), allowing unrestricted boot partition sizes on those platforms. The macro get-bootimage-partition-size needs to return an empty string in the case where the variable is not defined in order for consumers such as assert-max-image-size and get-hash-image-max-size that test its result using $(if) to properly disable the size check in that case. The indentation was causing the macro to return the string " " instead, which caused an unrequested size check to be inserted. Fix it by removing the indentation. A separate patch to avbtool makes it possible to omit the --partition_size argument when passing --dynamic_partition_size. Change-Id: Ie836feeb4c3e3b86d9c7950ff45933294cea9410 Bug: 142352330
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.