| commit | faa8e0b7e954bfb751994d3df4ce4af74954aac7 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Thu Apr 12 14:31:43 2018 -0700 |
| committer | Tao Bao <tbao@google.com> | Wed May 09 10:23:14 2018 -0700 |
| tree | e5a1e1a444f3999e7873839027b4f29f3a4df79d | |
| parent | a1dc661f7157d02d91d08746590eefc1c9b44167 [diff] |
releasetools: Use "ota-downgrade=yes" for --override_timestamp. We used to write a fake post-timestamp into package metadata for "--override_timestamp", which allows a package to be pushed based on the fake timestamp. This CL stops doing that by using the designated "ota-downgrade=yes" instead, but keeping the "--override_timestamp" flag for backward compatibility. Now both "--override_timestamp" and "--downgrade" allow pushing packages with downgrade timestamps. The only differenece is that "--downgrade" enforces a data wiping, because it's intended a real downgrade (based on Android version or security patch level). "--override_timestamp" serves the path of a legit "upgrade", but unfortunately with build timestamps in reverse order (e.g. the two builds are cut from different branches). With this CL, we write "post-timestamp" to all packages. Bug: 77811049 Test: Generate an incremental pakcage with "--override_timestamp". Test: Generate an incremental pakcage with "--downgrade". Test: python -m unittest test_ota_from_target_files Change-Id: I4ae4ce77cb600a06ffd9b15b6d4c730314aa0b79
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.