| commit | 75f7cf9a2d47964a0671bd4b2a61f3903107469a | [log] [tgz] |
|---|---|---|
| author | Justin Yun <justinyun@google.com> | Mon Oct 19 16:58:06 2020 +0900 |
| committer | Justin Yun <justinyun@google.com> | Wed Oct 21 03:39:22 2020 +0000 |
| tree | fd545a6f51ddc5f43dc37a781e3a3ab9d0afcadb | |
| parent | 8d9added3c3869cb38b814983666087c22f2353a [diff] |
Add fs_config_(dirs|files) for product and system_ext These files were added to devices with the fs_config_files_nonsystem module in base_vendor.mk. As they are partition-specific, move them to each base_<partition>.mk file. To add the fs_config_* files to the base_<partition>.mk files, it is required to define the fs_config_* regardless of the existance of partitions. Bug: 170282998 Test: build and check if they are installed. Change-Id: Ib8a2c75e2e0e93bb7030da981494e880f8465e5a
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.