| commit | 22195346ddd6cc0b4a5f9848019c10fb5df6ce7d | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Mon Dec 02 14:51:37 2019 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Mon Dec 23 03:41:59 2019 +0000 |
| tree | f0fdcf53c37055c1c3bcd81d2ae16b7ad0b16898 | |
| parent | be77c453a7a461f02a0986c473056e1398a4641d [diff] |
apex-libs-absence checks are removed The check is implemented in Soong via the apex_available property. For a module that should be in the APEX named "foo" and shouldn't be in any other APEX and also in the platform (the non-updatable part), the property can be set to "foo" (without "//apex_available:platform") to express the restriction and then Soong will enforce it. Bug: 128708192 Test: m Change-Id: Ia1aaaacd685f466447b61deae2849cb0aa83def3
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.