| commit | e9eb5f96e02c39178e846c2d3279a48244b5a444 | [log] [tgz] |
|---|---|---|
| author | Bill Peckham <bpeckham@google.com> | Fri Feb 01 15:52:10 2019 -0800 |
| committer | Bill Peckham <bpeckham@google.com> | Fri Feb 15 13:25:16 2019 -0800 |
| tree | 104dbcc291573786f0a45632b2e05efc588cac81 | |
| parent | dba735e9a52411bc8b7cc5e54359a981b6ce016e [diff] |
Adding initial merge_target_files.py script to merge two target files packages. This script takes as input two partial target files (one contains system bits, and the other contains non-system, or other, bits). The script merges the contents of the two partial target files packages to produce a complete target files package. Bug: 123430711 Test: Build two partial target files, merge, compare with full target files. Test: Validate merged target files via validate_target_files.py. Change-Id: Ic24acf43b86fc703fb4c970688b006291a1861f8
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.