| commit | a88d2da5878eb94a473a2ec3344f22c442f84a8d | [log] [tgz] |
|---|---|---|
| author | Yi-Yo Chiang <yochiang@google.com> | Thu Mar 18 18:29:48 2021 +0800 |
| committer | Yo Chiang <yochiang@google.com> | Mon Mar 22 05:41:23 2021 +0000 |
| tree | d0d59d0a541cb409fddeb03e81217d0918f1be18 | |
| parent | fd4844272c960b7fd9402d2e40bc34554cd819e8 [diff] |
Nextgen release: Don't build images that GSI don't need These images are never used by GSI. Building them is a waste of resource and a potential source of confusion, for they are packaged into the *-img-*.zip of GSI. Skip building them. Bug: 183068624 Test: "m dist" on GSI and check the build artifacts under OUT and DIST directories, and check the contents of *-img-*.zip Change-Id: Ic14cfdd10ed26d975b369ce128e4b284378219ef
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.