| commit | b6618c2ece126cc509b69076ec40fb540728df92 | [log] [tgz] |
|---|---|---|
| author | Spandan Das <spandandas@google.com> | Fri Oct 25 21:02:07 2024 +0000 |
| committer | Spandan Das <spandandas@google.com> | Mon Oct 28 18:18:26 2024 +0000 |
| tree | e9466fd124cd24167065badc6dd5bc3a51214abb | |
| parent | 49a6b38383d19538fc1ae3c9c29008cf7d955b2f [diff] |
Export some board config vars to autogenerate vendor-build.prop As part of the automatic vendor.img soong module generation, we will also autogenerate a vendor-build-$PRODUCT.prop and andorid-info-$BOARD.prop soong module. These will eventually be checked-in. The kati vendor.img will still use the kati built vendor build.prop file. Bug: 374371755 Test: diff in contents for aosp_cf_x86_64_phone https://paste.googleplex.com/5766413037076480 Summary - timestamp change (expected) - ro.hwui.use_vulkan changes from "" to false, but I think this is functionally equivalent Test: presubmits Change-Id: I66dafadd286a5c6047dc99562ab32f72eda509ee
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.