| commit | d8cc1352b5c125dea44da511804de3db9691037a | [log] [tgz] |
|---|---|---|
| author | Inseob Kim <inseob@google.com> | Wed Jan 06 23:10:41 2021 +0900 |
| committer | Inseob Kim <inseob@google.com> | Wed Jan 06 23:10:41 2021 +0900 |
| tree | d25fcad2c02443c615369b701aff88d55f24f61e | |
| parent | bc86b7b2fb9ad5cf668c8fa44d3c85f19774fa38 [diff] |
Implement directed vendor snapshot Vendors can now generate only needed modules by setting the following Makefile variables: - DIRECTED_VENDOR_SNAPSHOT: set to true - VENDOR_SNAPSHOT_MODULES: list of snapshot candidates e.g. DIRECTED_VENDOR_SNAPSHOT := true VENDOR_SNAPSHOT_MODULES := toybox_vendor sh_vendor libbase libcutils ... Bug: 157967325 Test: m dist vendor-snapshot after setting those in BoardConfig.mk Change-Id: Iea1ddbe78e143316fb6cb5027de90b9c83252f80
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.