commit | c8fd08dfd302bd2447023fccfcd895b373981d1e | [log] [tgz] |
---|---|---|
author | Spandan Das <spandandas@google.com> | Mon Jan 06 20:20:15 2025 +0000 |
committer | Spandan Das <spandandas@google.com> | Mon Jan 06 20:25:28 2025 +0000 |
tree | 437dc0340075f054f8aebfd3f94f40ea7f14faba | |
parent | 7b07f2f1a7bb4f57bc9e72ebed0e429f84d2c36b [diff] |
Use fixed timestamp in img files using an environment variable This creates hermetic img files, and will be used to assert equivalence between make and soong built img files. An alternative would be to use the timestamp from build_date.txt, but that causes a full push on the first adb sync (b/385995921) Test: spot checked that system_ext.img built by make and soong are bit identical (with notice files commeted out) Change-Id: I038c1ee31dff6211e38db0ba63b993f3856c4c0f
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.