| commit | 56c980af5cf0d09f6cbdf500b7e32b4cba8411f1 | [log] [tgz] |
|---|---|---|
| author | Spandan Das <spandandas@google.com> | Thu Dec 12 01:24:40 2024 +0000 |
| committer | Spandan Das <spandandas@google.com> | Thu Dec 12 01:35:08 2024 +0000 |
| tree | 068607b5fc4dce311bf2e3b370edf8049ccf34c0 | |
| parent | 15a0df840e7093f65518003ab80cf24a3d9e8e6a [diff] |
Parse fingerprint and timestamp unconditionally build_image.py adds `fingerprint` and `timestamp` to the config object by doing some string processing, but does so only when mount_point is missing in the input property file. This makes this unavailable to Soong's android_filesystem modules, which always provide a mount_point in the property file. This CL creates a `TryParseFingerprintAndTimestamp` function to make this logic common to empty and non-empty `mount_point` property files. Bug: 376539388 Test: lunch aosp_panther-trunk_staging-userdebug Test: m out/soong/.intermediates/packages/modules/Virtualization/guest/pvmfw/pvmfw_img/android_arm64_armv8-2a_cortex-a55/pvmfw.img (a bootimage module) followed by rm repeatedly Test: sha remains consistent Change-Id: I602815338d8938cc81ba44d2e9aa1a9ff8afccde
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.