commit | bfc51efa971c62fb3fa04d3904312c1589614fce | [log] [tgz] |
---|---|---|
author | Daniel Norman <danielnorman@google.com> | Wed Jul 24 14:34:54 2019 -0700 |
committer | Daniel Norman <danielnorman@google.com> | Mon Jul 29 16:30:56 2019 +0000 |
tree | d096b47457e0f03ea927fbc013c60924129a61e8 | |
parent | 6f8e3da0356abea6466ac08796022cc9bf698ffc [diff] |
Adds new merge builds script for use in merging two non-dist builds. Bug: 137853921 Test: python -m unittest test_common Test: python -m unittest test_merge_target_files Test: Built two partial builds without dist. Ran out/host/linux-x86/bin/merge_builds. Flashed using `fastboot flashall`. Device boots. Change-Id: Iffd0a447cdf19a7775a813b4b896178aa6f861f3
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.