commit | 4b25c90e528676f17928cf810ac8dcf179904bbb | [log] [tgz] |
---|---|---|
author | Bob Badour <bbadour@google.com> | Tue Jan 28 13:23:39 2020 -0800 |
committer | Bob Badour <bbadour@google.com> | Wed Feb 26 16:49:28 2020 -0800 |
tree | 57aa0ff0bf152ad23dcddb9e15652cf344bfb118 | |
parent | 372831200507edacc602be017f4c5ac3c5964283 [diff] |
Partition the targets for notice files. Partition the targets into those appearing in system images, those appearing somewhere unreadable by the Settings UI, whose notices must appear in a readable system image, and those not appearing on the device thus not needing notices. Assert no other targets appear under $(PRODUCT_OUT). Test: manually built and tested phone image Change-Id: If82cb36f98f8e6066d1c67bb4d15976be433d403
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.