commit | df6fdeef04a1a7389b513885b00fe8d1a344cbfe | [log] [tgz] |
---|---|---|
author | Peter Kalauskas <peskal@google.com> | Fri Apr 28 11:45:07 2023 -0700 |
committer | Peter Kalauskas <peskal@google.com> | Thu May 04 11:02:17 2023 -0700 |
tree | d2eea8cb327ee375b6632bea6a9c13c715909b28 | |
parent | 48033761bf29b383eb707cf8c620a48ee3c41c2d [diff] |
New targets for building files needed by adb sync Create new phony build targets for sync_system, sync_vendor, sync_product, sync_system_ext, sync_odm, sync_vendor_dlkm, sync_odm_dlkm, and sync_system_dlkm. These build just the files on the associated partion, (e.g. /system_ext), but not the image file (e.g. system_ext.img). Like sync, but just for a single partition. Test: modify System UI, m sync_system_ext && adb sync && am restart Change-Id: I5aa40d7018e029a57114681dd16db3f1e5651a63
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.