| commit | 58c4535b7e61f513529af462838dc47330e9a538 | [log] [tgz] |
|---|---|---|
| author | Bob Badour <bbadour@google.com> | Thu Sep 02 11:28:23 2021 -0700 |
| committer | Bob Badour <bbadour@google.com> | Thu Sep 09 20:09:13 2021 +0000 |
| tree | f04912df6e037462cea216bbadf35e5d03ca2415 | |
| parent | 355f34595656fcc624817bd4e9413c157a0d3113 [diff] |
Re-call BUILD_NOTICE_FILE for modules that add deps The normal pattern is: 1. Set a bunch of variables like LOCAL_MODULE 2. Include a makefile specific to the module type 3. The included file in turn includes base_rules.mk 4. At the end of base_rules.mk, it include notice_files.mk 5. The included file declares a build rule and finishes. The below files included for some module types add additional dependencies after returning from base_rules.mk, which are not reflected in the notice files. Including notice_files.mk a 2nd time adds these dependencies. Bug: 68860345 Bug: 151177513 Bug: 151953481 Test: m all Test: m systemlicense Change-Id: I030399ffb13a2cfb58cf583ae5a2e418f5dbc534
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.