| commit | 74a6a0a32ac0e4098f9b101056007b9dd976518a | [log] [tgz] |
|---|---|---|
| author | Bob Badour <bbadour@google.com> | Fri Jul 17 20:47:42 2020 -0700 |
| committer | Joe Wang <wangzhou@google.com> | Tue Jul 21 22:47:29 2020 +0000 |
| tree | 680ee2c8ae13b9d5e7434b2f61f5762144347be1 | |
| parent | 5486ee7365472206930dc67d8f876af833805746 [diff] |
Add support for combining the notices from 2 roots. Apparently needed for cts tests due to apks putting intermediate files under TARGET_OUT even when going to HOST_OUT. Test: m with and without change verified no differences in notice files Bug: 141258651 Change-Id: Iea50b6bd9af9452a2600c97e2f7cb89218b9be7f (cherry picked from commit 5e9e1fbe836da8bfc829535043463c37a929b460) Merged-In: Iea50b6bd9af9452a2600c97e2f7cb89218b9be7f
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.