commit | 670c587c09ae68e72077f5bca70e71feebc523cb | [log] [tgz] |
---|---|---|
author | Cole Faust <[email protected]> | Thu Mar 31 17:25:20 2022 -0700 |
committer | Cole Faust <[email protected]> | Thu Mar 31 17:30:35 2022 -0700 |
tree | cf560ec4c97cc9abd3a0c0e04a0b79034cb17d22 | |
parent | bcabb923dcc3748a015204a9684e9b2135d612e3 [diff] |
Fix inheritance order The children to inherit from were not sorted. This wasn't a problem for list variables, because all those inheritances get merged together based on the @inherit/ values in the list variables. But for single value variables it made a difference. Bug: 226206409 Test: ./out/rbcrun ./build/make/tests/run.rbc Change-Id: Ib56bbb91a79fe8c7cb780c253f5bd8d6c0e87765
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.