commit | 89418f058e5412a871be3db4bb4c8967b33ce058 | [log] [tgz] |
---|---|---|
author | Tamas Petz <tamas.petz@arm.com> | Mon Feb 03 15:40:15 2020 +0100 |
committer | Tamas Petz <tamas.petz@arm.com> | Mon Feb 10 11:34:48 2020 +0100 |
tree | c68e632012648b96ddaf469e4ab4d9d049391f84 | |
parent | 1dffdf84d13e61e8f2e4cd621596dff754dafffe [diff] |
core/Makefile: pass value of PRODUCT_USE_DYNAMIC_PARTITION_SIZE Regardless of the value of PRODUCT_USE_DYNAMIC_PARTITION_SIZE "use_dynamic_partition_size=true" is passed to build_image.sh. Pass the value of PRODUCT_USE_DYNAMIC_PARTITION_SIZE just like it is done for other properties. Test: 1. build a target with fixed partition sizes and "PRODUCT_USE_DYNAMIC_PARTITION_SIZE := false". 2. check the value of "use_dynamic_partition_size" in the corresponding system_image_info.txt. 3. repeat steps 1 and 2 with this fix and see the difference. Change-Id: Ia121d3d67f554f8ae4e211ad4e2c381a43409f01
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.