commit | 8821d644811d866f22bac4dc46c8cf5c188a6e48 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Mon Aug 05 12:05:45 2019 -0700 |
committer | Tao Bao <tbao@google.com> | Mon Aug 05 12:57:41 2019 -0700 |
tree | 1439790a3a05aaf82ec2008ff3e6d429b1ba27ca | |
parent | 6240872250ffe443d15efef5ad6388509ca44555 [diff] |
Build and use ota_from_target_files as a module. Bug: 63866463 Test: TreeHugger Test: m -j otapackage Test: `m -j otatools-package`. Check bin/ota_from_target_files is available. Build an OTA package with standalone otatools. Change-Id: I533dee1c6997d233601e7f4eae637ff5743ed637
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.