| commit | 616e7fd9b6460455f75506b4db157915bd300807 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Thu Sep 16 14:50:08 2021 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Thu Sep 16 14:54:38 2021 -0700 |
| tree | 9187d39d20b76af0728b6aa242712846c8ef7d3f | |
| parent | dfc9d7912f1fe368025d01fe7128a413a98b74ac [diff] |
Stop disting monolithic SDK for Mac SDK builds The Mac SDK build is being reduced to just the build-tools and platform-tools packages. I'm still working on refactoring those builds not to require the monolithic SDK to be built first, but we can at least stop distributing it (and other related files) now. Most of these checks can likely go away once the build refactor is complete, since we'll be able to move away from the `sdk` target to something more specific. Right now there's a lot of logic around sdk being in MAKECMDGOALS that I don't want to unravel with the current build logic. Bug: 187222815 Change-Id: I1f711ce063170e41078ad4a125bcd77340a1746c
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.