commit | 53940fd2ba4103d3bdc07cf9b1a8cbc02158c44f | [log] [tgz] |
---|---|---|
author | Tom Cherry <tomcherry@google.com> | Thu Jun 14 12:19:19 2018 -0700 |
committer | Tom Cherry <tomcherry@google.com> | Thu Jun 14 13:29:32 2018 -0700 |
tree | 4ea57d8e136c06bf2217348427bc75512730ba09 | |
parent | bc965aa7a9076f700114ea29d48883c476936692 [diff] |
Always create /vendor/etc/{passwd,group} Previously we only created these if the device set TARGET_FS_CONFIG_GEN, however there are now other targets that want to depend on these. Instead of having those targets conditionally depend on them, we always create them, defaulting to blank contents (by reading /dev/null for TARGET_FS_CONFIG_GEN). Test: builds succeed Change-Id: Ie95286f5a800d891022eb66cd6fefcc967000c2e
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.