| commit | bbd95df172f8712057d93109d3d145624b26f324 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <[email protected]> | Wed Nov 25 11:51:49 2020 +0000 |
| committer | Anton Hansson <[email protected]> | Tue Dec 15 11:42:39 2020 +0000 |
| tree | cf415fe41777380c54200f33a95c0193a1aed34c | |
| parent | 1a9d81a06b7c794b297c13bc2d57f38c5f522b09 [diff] |
Add devices suitable for single-arch module builds Prior to this the generic_* devices were typically used for this purpose. There are a few reasons to create new specific ones: - the generic_arm64 device has a hack specifically for building multi-arch packages that we want to avoid - the generic_* devices include a bunch of emulator config that does not make sense for unbundled builds Bug: 172256440 Test: verify unbundled builds migrated from generic_* don't change Merged-In: Ia937461aa24a5d5b542f8688a1b71ac3fdeb596b Change-Id: Ia937461aa24a5d5b542f8688a1b71ac3fdeb596b
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.