commit | edf124780fceac9a0d9b018d8c360cdcb014e396 | [log] [tgz] |
---|---|---|
author | Daniel Norman <danielnorman@google.com> | Wed May 22 10:47:08 2019 -0700 |
committer | Daniel Norman <danielnorman@google.com> | Sat Jun 01 04:39:46 2019 +0000 |
tree | dd9694d75da7ae9af0844f74c0d55243b006140e | |
parent | cd56c0df95f2b4b275ad3c876a848cd2ce90a6d8 [diff] |
Adds validation check that certain partitions come from a single build. This is to prevent a user from accidentally including files from the wrong build. For example, adding any SYSTEM/ line to other_item_list while keeping SYSTEM/* in system_item_list would cause the other build to introduce an extra or changed file in the system image. Bug: 132730710 Test: python -m unittest test_merge_target_files Change-Id: Ic1178cdc9b991114f293ff3f2b4e6054e06647c6
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.