| commit | cfbbec902dae82b908ac0e73039e44f91d8ef59a | [log] [tgz] |
|---|---|---|
| author | [C <spandandas@google.com> | Tue Jun 24 02:46:40 2025 +0000 |
| committer | [C <spandandas@google.com> | Tue Jun 24 03:09:13 2025 +0000 |
| tree | 28c7b35e928cc9d7e3b88c8f75edf29403d776ff | |
| parent | 0b84e3a8418ef1358379e8cb914f82c760ba237a [diff] |
Reapply "Reapply "Export pvmfw properties to soong"" This reverts commit cbddf1489fbe02e09a348cbed0273228f08ea0c2. Some products use a product config variable to override the default pvmfw mdoules (`pvmfw_img` and `pvmfw_bin`). This CL exports additional product config variables to support this override. Test: lunch'd failing product followed by m nothing Bug: 424812534 Change-Id: I56bed537d3df60c2bc44eb3bdf8b92b019185696
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.