commit | 7f25f2aed9b9152b3da4a96c4dcc7b9b33d357fd | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Thu Apr 18 10:10:34 2019 -0700 |
committer | Dan Willemsen <dwillemsen@google.com> | Thu Apr 18 17:16:50 2019 +0000 |
tree | c4702ed4c073854e5f33b447f1570d2d14e8014e | |
parent | aa0aa5e5c82c80b9fdea685a172ab88309ef0c56 [diff] |
TARGET_FS_CONFIG_GEN is a list, not a single path Bug: 130787336 Test: m oemaids_header_gen oemaids_headers passwd group Test: Set TARGET_FS_CONFIG_GEN to a list of paths Change-Id: I5186b378fea8865f46cfd891420ba576f36e2565
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.