commit | 36ce326f95cdadaa30edce331d8ec07d5270ac78 | [log] [tgz] |
---|---|---|
author | Dennis Song <denniscy@google.com> | Wed Sep 13 06:53:00 2023 +0000 |
committer | Dennis Song <denniscy@google.com> | Fri Sep 15 06:20:19 2023 +0000 |
tree | 8662243ef69f52c0030228780ebfb38c6a7238c9 | |
parent | 91646be0a5d6ce23ee45172e6ad4891d0bf0d5e4 [diff] |
Respect framework partition set while merging meta files The framework_partition_set would be generated from framework_item_list and we should respect this partition set while merging META/ab_partitions.txt. This is to handle the case when we use a complete merged target files package as the framework-target-files, where its ab_partitions.txt may have non-framework partitions. So we need to filter them out to prevent from the merged meta file has some partitions that don't exist. Test: merge_target_files && add_img_to_target_files && img_from_target_files && flash device Bug: 300193612 Change-Id: I0a76d706a20dcaffa2533278db7383563f03ec02
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.