commit | 30df8b4e2ee20639bdfdef475374ea539b54bfd7 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Mon Apr 23 15:32:53 2018 -0700 |
committer | Tao Bao <tbao@google.com> | Mon Apr 23 16:00:14 2018 -0700 |
tree | aab21bc7aa82ae7ba278b73cc86d1cf8d99e6f37 | |
parent | ffb88397f74a128ddf34eb6639b588912c26065b [diff] |
releasetools: Group the option descriptions in ota_from_target_files.py. This CL separates the options into three groups (excluding the global options provided via common.py). - Non-A/B OTA specific options; - A/B OTA specific options; - Common options that apply to both. It mostly reshuffles the lines, with minor change to "--verify" that removes the obselete remounting behavior (which doesn't apply to block-based OTA). Hopefully this makes the expected behavior of some options less confusing. Test: `build/make/tools/releasetools/ota_from_target_files.py` Change-Id: I194ea52c4f7d6a3c7f34531abbcf3fdc7b7f4fa8
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.