commit | e691aef7b1668072870a80f5c45b2f41f1e1d476 | [log] [tgz] |
---|---|---|
author | Bowgo Tsai <bowgotsai@google.com> | Tue Jan 04 14:33:43 2022 +0800 |
committer | Bowgo Tsai <bowgotsai@google.com> | Tue Jan 04 17:41:01 2022 +0800 |
tree | 068a02939857a81b548754c8edc54c451ee406f6 | |
parent | 8c861cec97383a30eaef1ea4f68b2ed04f41f5b8 [diff] |
Calls check-and-set-avb-args() when the system.img exists Some targets, e.g., the newly added `gki_arm64`: https://r.android.com/1935340, have no system.img. To avoid the build error when making the vbmeta.img on a no-system-image target, only sets system.img's AVB settings when it exists,. Bug: 212486689 Test: `lunch gki_arm64-userdebug; make` with BOARD_AVB_ENABLE := true Change-Id: I5e3c531e74116e421506a86ffce83848e7a9d6ea
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.