commit | e6d547d53a841a311e1b080e09afbc8beb3e4ec7 | [log] [tgz] |
---|---|---|
author | Bryan Henry <bryanhenry@google.com> | Tue Jul 31 18:32:00 2018 -0700 |
committer | Bryan Henry <bryanhenry@google.com> | Tue Jul 31 18:32:00 2018 -0700 |
tree | eec2c9f82ad2aa48c56aca05bb708ad438eab4d2 | |
parent | bb937a6b69f0d31366b9dbf3d4200a00747f30e3 [diff] |
Fix 2009-01-01 timestamps in releasetools to always be UTC The usage of datetime.fromtimestamp previously resulted in the build or signing machine's local timezone affecting the Unix timestamp ultimately applied to images generated by add_img_to_target_files. The go/ab build outputs would use 2009-01-01 00:00 UTC, for example, but local builds and the release signed images (generated through go/ab-sign) would use 2009-01-01 00:00 PST. This change makes the timestamps always use UTC. Bug: 80600931 Bug: 80093599 Test: 'm -j droid dist' and verified timestamps in resulting target_files zip. Change-Id: Ic2a19591519850c249f78254e1464aa6839bfc6c
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.