| commit | c3b841a422f5a177c54912f0e573c9c7a2beb55c | [log] [tgz] |
|---|---|---|
| author | Tianjie <xunchang@google.com> | Mon May 24 15:27:05 2021 -0700 |
| committer | Tianjie <xunchang@google.com> | Wed May 26 11:19:45 2021 -0700 |
| tree | 528c55f6eac4e51805500abb7129e265009b3c20 | |
| parent | ec11d42e3b29c2e9f679e8882a19cbcc4f427e1d [diff] |
Enable a prop to determine the new figerprint is enabled VTS and some other tests would replace the system images with GSI. To put the correct fingerprint in the test report, we need to know if the new fingerprint format is in use. So, add a vendor build prop. OEMs are reponsible for setting this build prop, or using other ways to put the correct fingerprint in the test report. Bug: 188824341 Test: boot the device, check build prop Change-Id: I6bc7f01903865fc2c256d209debdab68cd9d1bb3
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.