| commit | 1c08360ca8c270b7a16091243623399b50f29b51 | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Fri Apr 08 18:09:22 2022 -0700 |
| committer | Cole Faust <colefaust@google.com> | Tue Apr 12 15:25:14 2022 -0700 |
| tree | 9366f00cb7f59604bda4f68cdd1b71f7c76d2f1f | |
| parent | ea935b5ad9f19e5c44663feed3a620ea8c54c467 [diff] |
Evaluate intermediate products properly When an intermediate product is evaluated, it needs to act as if it's the only product being evaulated. However, currently, if it inherited a makefile that was also being inherited by the overall top level product via a different path, it would not get the values from that makefile. Copy the configs dictionary before evaluating each product that needs artifact path requirements, and create seperate postfix orders for all of them that don't contain any products that they don't inherit from. Bug: 221312707 Test: ./out/rbcrun ./build/make/tests/run.rbc Change-Id: I235ad78d587a2e315ba446b5e126d8f6d0fbbea7
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.