commit | 1683198010f7d1e565fc53e0690e6a1808eaa819 | [log] [tgz] |
---|---|---|
author | Anton Hansson <hansson@google.com> | Fri Mar 22 14:10:19 2019 +0000 |
committer | Anton Hansson <hansson@google.com> | Fri Mar 22 17:25:43 2019 +0000 |
tree | 80b225611524b1197f2b617c58ea64bfad584db9 | |
parent | 07fa9b13b44178f926d86668e89a25a52be25a99 [diff] |
Set file system types for mainline_arm64 partitions This config was in a weird state where it sets the OUT directory for these partitions but not the file system type. Within the build system, both of these variables are used interchangeably to check whether these partitions are expected to be present. A typical mainline device is expected to /vendor and /product, so just add these. Bug: 120974093 Test: make Change-Id: I803d7afdcadc37e4384ae80f08bc1c8db535d2f4
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.