| commit | 23ee375a4aa4885c4a54d649d639c80ee5c605a8 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Fri Sep 24 15:48:03 2021 -0700 |
| committer | Colin Cross <ccross@android.com> | Fri Oct 29 15:43:39 2021 -0700 |
| tree | 0c4d8b76b18fbb9a5d12696d20effa3c8114c9f5 | |
| parent | 09f68abca769321b0d6c58d9581f76fb3181667c [diff] |
Support generating install rules in Soong Support moving some install rules into Soong by allowing Soong to provide a Makefile containing install rules, and by skipping parts of base_rules.mk when Soong already created an install rule. The install rules are exported as a Makefile instead of directly in Soong's build.ninja file so that base_rules.mk can add dependencies from the `required` property that are hard to resolve in Soong. Bug: 204136549 Test: m checkbuild Change-Id: Ife2964d76469b385e90c0c5f6adf21bd2b5e8bf6
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.