| commit | fd2e967af05abd37983af4a2c62e7ba96f5577e4 | [log] [tgz] |
|---|---|---|
| author | Sangmin Lee <sangmin5.lee@samsung.com> | Wed Aug 21 17:01:07 2024 +0900 |
| committer | Sangmin Lee <sangmin5.lee@samsung.com> | Thu Aug 22 15:23:47 2024 +0900 |
| tree | b53ecd8866c377b7ea27f72c247ff71a0190869c | |
| parent | cb56fa972b50151924282035545f0024cac9c25e [diff] |
Optimize: Reduce vendor target build files Prevent system/% files from being built by BUILDING_SYSTEM_IMAGE and data/% files from being built by BUILDING_USERDATA_IMAGE 1) Address issue where system/% files were being built even when PRODUCT_BUILD_SYSTEM_IMAGE was false. This change reduces the ninja targets for aosp_cf_x86_64_phone_vendor-trunk_staging-userdebug from 140,427 to 57,303 Test: lunch aosp_cf_x86_64_phone_vendor-trunk_staging-userdebug ; m 2) Resolve issue where data/% files were being built during "m dist" even if PRODUCT_BUILD_USERDATA_IMAGE was set to false Test: Set any module to install at data partition using LOCAL_MODULE_PATH=$(TARGET_OUT_DATA)/app lunch aosp_cf_x86_64_phone_vendor-trunk_staging-userdebug ; m dist Check the contents at out/target/product/vsoc_x86_64 and out/dist Change-Id: I2a914339231d57598a6f30fc83fd8203d4107a11
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.