| commit | e73c5a074dd89ef3409116e8334f1001ecbc31c0 | [log] [tgz] |
|---|---|---|
| author | Yo Chiang <yochiang@google.com> | Mon Jun 01 17:55:16 2020 +0800 |
| committer | Yo Chiang <yochiang@google.com> | Thu Oct 29 10:48:17 2020 +0000 |
| tree | 058245a78af405c5f19195d8876d195841829094 | |
| parent | 67e13411000b075e9e74cbb8263d42c1c2983f53 [diff] |
Fix missing required dependency caused by circular dependency Fix a bug where if module A requires module B, and for whatever reason module A and B have some common installed files, then all required dependencies of the common files would be lost. For example: ``` # A requires B ALL_MODULES.A.INSTALLED := a ALL_MODULES.B.INSTALLED := a b ``` Right now the build system wouldn't generate any dependency for `a`. However the correct behavior should be: `a` has a order-only dependency on `b`. Bug: 157444528 Test: Check generated build-*.ninja Change-Id: Iec60231f6597ec46077393d1defa109b9c07b208
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.