| commit | e85ec84eef1f3f2fa778912684931d8c3935715f | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Tue Jun 26 14:03:38 2018 +0100 |
| committer | Anton Hansson <hansson@google.com> | Wed Jun 27 11:15:59 2018 +0100 |
| tree | 3917e4caa5ab0b8dcef2b573badcc036821cdc0e | |
| parent | a314fc0166d58e2f866baa91e704b39bf7cb97c9 [diff] |
Split up fs_config_* modules per partition. This was already done for partitions other than the system partition. Add new, separate "_system" targets, and add new phony modules which collects _system and _nonsystem targets for now. Update the base_system.mk file to only depend on the system module, and put the other ones in base_vendor.mk for now. Bug: 80410283 Test: make fs_config_dirs[_*] fs_config_files[_*] and verify output Change-Id: I7843578dbb9f27edf4c1e5b4a795a530f79e0be1
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.