commit | 0ec64ac0aac328374a640a04f2c02ce587c68c84 | [log] [tgz] |
---|---|---|
author | David Anderson <dvander@google.com> | Fri Dec 06 12:21:18 2019 -0800 |
committer | David Anderson <dvander@google.com> | Wed Dec 11 22:32:00 2019 +0000 |
tree | 71627ebfd4953885ede2cf03483e3481b876557a | |
parent | 3b500a7ec3c48fd226d5963a4d42f2401ae19b89 [diff] |
releasetools: Generalize base_fs_file handling. Share the code to handle base_fs files rather than duplicate it for system/vendor. At the same time, add support for system_ext and product partitions. Bug: 139201772 Test: manual test Change-Id: Ib1b7c018c828901e24eefc01e3faead03e77bc2d
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.