| commit | c497641e6f05a1252d323c1d4bfbf1d618f6e381 | [log] [tgz] |
|---|---|---|
| author | Inseob Kim <inseob@google.com> | Tue Jan 05 20:00:08 2021 +0900 |
| committer | Inseob Kim <inseob@google.com> | Thu Jan 07 13:56:33 2021 +0900 |
| tree | 38b027fd889ee6a30a16ee1dbd0fe54f8239cccf | |
| parent | 939e511748991fce7a8c16ae6aeb215c90f5afe6 [diff] |
Implement fake vendor snapshot A fake vendor snapshot is a vendor snapshot whose prebuilt binaries and captured headers are all empty. It's much faster to be built than the real vendor snapshot, so users can exploit the fake vendor snapshot to reduce the size of vendor snapshot they need, by installing the fake snapshot and then inspecting the ninja dependencies. Bug: 157967325 Test: m dist vendor-fake-snapshot Change-Id: I7fa5d5033a296965b21e840765cc7fe02fd1f44e
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.