| commit | 01e381954ba45da2b69dcddf5c2fb475e789cc98 | [log] [tgz] |
|---|---|---|
| author | Håkan Kvist <hakan.kvist@sony.com> | Thu Apr 13 21:49:19 2023 +0200 |
| committer | Håkan Kvist <hakan.kvist@sony.com> | Fri Apr 14 10:36:04 2023 +0200 |
| tree | e93b219732138e7c8bdc8667bf6e3c295d71c3e9 | |
| parent | 64bfc41359f8502569feee49c892d4f0f0399798 [diff] |
Order entries in apex_info.pb
Adding the entries in apex_info.pb in sorted order makes it easier to
compare ota packages generated between the same source and target on
different computers/environments, ideally the generated ota zips should
be identical.
os.listdir() was used to find the apex files which should be
included in apex_info.pb. listdir() does not guarantee any order,
solution is to sort the result to ensure consistent order.
Bug: 278095305
Test: Manual. Confirm that apex_info.pb is generated sorted
protoc --decode_raw < apex_info.pb
Change-Id: I2851d207f828a6ac31e63e20c9025965ac4b0eba
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.