| commit | e30a6a6df9bf547f53283b8332c366abf327888e | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Mon Aug 27 10:57:19 2018 -0700 |
| committer | Tao Bao <tbao@google.com> | Mon Aug 27 11:03:55 2018 -0700 |
| tree | e2d071c92e4886cd9ec5bbcf99cceba570a4923a | |
| parent | 22f28aa1b56e8da105a306a158ed41f446d56410 [diff] |
releasetools: Use int value of FIXED_FILE_TIMESTAMP. Otherwise it gives a floating-point value (i.e. 1230768000.0). e2fsdroid (i.e. the user of the value) didn't complain though, because it calls strtoul(3) without checking endptr. Bug: 80600931 Test: `m dist` with aosp_taimen-userdebug, check the build log. Change-Id: I7467a60c947134b42f079c7a57fb8a9a9d4277da
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.