| commit | b45129d2185155dcef39a2e948db9060d057efe1 | [log] [tgz] |
|---|---|---|
| author | Spandan Das <spandandas@google.com> | Mon Dec 02 19:39:17 2024 +0000 |
| committer | Spandan Das <spandandas@google.com> | Mon Dec 02 19:46:26 2024 +0000 |
| tree | 07217dc473e0cc887788095fec4cbd924c265127 | |
| parent | 3475af96e614f040876d763bbca37b21a7fbf504 [diff] |
Export PRODUCT_FSVERITY_GENERATE_METADATA to soong This will be used to conditionally generate fsv_meta files in the autogenerated soong partitions. Test: lunch sdk_phone64_x86_64-trunk_staging-userdebug Test: Ran the diff test tool on autogenerated soong system image Change-Id: I9b7487d49fae079fa8e6ba3a89712da56ad4ed71
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.