| commit | d3bf67e1d3d480ec78777a81c1ee49c4d2c452cb | [log] [tgz] |
|---|---|---|
| author | Tianjie Xu <xunchang@google.com> | Wed Jan 10 10:55:19 2018 -0800 |
| committer | Tianjie Xu <xunchang@google.com> | Wed Jan 10 12:23:57 2018 -0800 |
| tree | ca5f691b5a55053326a9d7d058f231234ea75c73 | |
| parent | e3692095a1f201071fc50f5940094388bac81846 [diff] |
Sort the split transfers to generate a determinate package We split large apks and generated patches for them in parallel, resulting in nondeterminate packages between different runs. This CL sort the split transfers by target name first; and then add them sequentially to the final transfer list. Also fix a side effect where we may generate a wrong sha1 for split ranges due to synchronization error. Bug: 71770360 Bug: 71759418 Test: Generate the package several times, compare the log and the transfer list. Change-Id: I2a49e22594d59ffaa98b11edc776be4e3c4c561f
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.