| commit | 5bece83c597b4ee6a4c1345d12a8cd63c1e7c625 | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Fri May 18 17:46:04 2018 -0700 |
| committer | SzuWei Lin <szuweilin@google.com> | Mon Sep 03 07:09:03 2018 +0000 |
| tree | 061b4426c0f4e1ecca5ec681d3cbda8b9db20bc1 | |
| parent | 29acab8838a19df634f89295a4cb7655bb022f85 [diff] |
Add PRODUCT_USE_LOGICAL_PARTITIONS
Test: Set a device with PRODUCT_USE_LOGICAL_PARTITIONS,
boot, examine /proc/cmdline
Test: build with USE_LOGICAL_PARTITIONS=true
Fixes: 79885414
Change-Id: I593b457786f3cf1bc50dedbc9b603e5408461bcc
Merged-In: I593b457786f3cf1bc50dedbc9b603e5408461bcc
(cherry picked from commit ef4cd71ebfd599fbd380fe2223f18a66c2b262ad)
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.