| commit | 1cfe25155ea34b7b6d06b0a6f82e9cbce366fe46 | [log] [tgz] |
|---|---|---|
| author | xunchang <xunchang@google.com> | Tue Feb 19 14:14:48 2019 -0800 |
| committer | xunchang <xunchang@google.com> | Wed Feb 20 15:32:09 2019 -0800 |
| tree | 81611b508312e5ee0e255aa2bf6d93abfcc714d7 | |
| parent | 5fa7e2fa2cfdd17d7cd24760ec3b968dfe110635 [diff] |
OTA: Add an option to dump the metadata in ota package Add a flag to write a copy of the metadata to a separate file. Therefore, users can read the post build fingerprint without extracting the OTA package. Bug: 124783265 Test: Check the dumped metadata file after generate A/B and non-A/B OTA. Change-Id: I8918aec87bb81906ef0a7eee774178e9f689d91d
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.