| commit | 349dc0793379cfbed1e126813f6b53fb25c7ceda | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Sun Oct 17 00:28:39 2021 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Sun Oct 17 00:28:39 2021 -0700 |
| tree | 6dd6d99c45c8d02735008f0305c12b2bafa004e9 | |
| parent | 3ef140cf64c02114e0a7bc8b1096577bef7b7b82 [diff] |
Shrink Mac builds Device builds are no longer supported on Mac, but we do support building various host tools, including the SDK build-tools and platform-tools packages. All of these are defined in Soong now, so we stop reading all the Android.mk files, and defining and depending on the device output targets. Bug: 187222815 Test: `m`, `m dist`, etc on Mac Change-Id: Ibb19756d44f2cbc6948381043115718ffc3f4b7d
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.