| commit | c62d15f07791c76cea72c7a00cafd4450163a699 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Fri Jul 13 11:07:07 2018 +0100 |
| committer | Anton Hansson <hansson@google.com> | Wed Jul 18 15:52:57 2018 +0100 |
| tree | 1d912821df41848e85e76ff4aab1f5c9dc032161 | |
| parent | 401fada3f59c6fc8de8429765b1fba373d6d939a [diff] |
Skip auto-gen rro packages for path requirements. The way these packages are currently added to the build is via modifications in product makefiles inheriting from mainline_system, but with have the side effect of changing the REQURIED modules for the source of the auto-gen RRO package. Whitelist auto-generated RRO packages from the path requirement checks for now. Bug: 80410283 Test: make Change-Id: Ib070e28e0ef87a57adfaedf6456585e8bfa29dd3
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.