| commit | 323940e87bb6758dfe2606326d7a6e850cead4e8 | [log] [tgz] |
|---|---|---|
| author | Spandan Das <spandandas@google.com> | Fri Dec 13 00:46:04 2024 +0000 |
| committer | Spandan Das <spandandas@google.com> | Thu Dec 12 18:05:41 2024 -0800 |
| tree | d3ca0f994705d9b005a35ef1150b65eea8f3f3c2 | |
| parent | 4d8612503def230bebeb2a10aae4c6af4b722ead [diff] |
Add a build_datetime_file arg to build_image.py If this file exists, build_image.py will use the timestamp from that file as the mtime of the different indoes in the output img files. build_image.py already supports hermetic img files (e.g. via use_fixed_timestamp / timesatmp in the property file), but this feature is useful since it allows build_image.py to directly use the build_date.txt file created by android builds. Bug: 383357338 Test: lunch aosp_cf_x86_64_phone-trunk_staging-userdebug - export BUILD_DATETIME=10 - commented out installed_*_notice_xml_gz in build/make/core/Makefile Test: verified that the following .img files are bit identical in top of CL stack odm,system_dlkm,vendor_dlkm,odm_dlkm Change-Id: I1cba5f426268d3a60de709ea4cd8bc154022bdf9
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.