| commit | 2be97d9d966396c29011bc102cfde320ab9fb347 | [log] [tgz] |
|---|---|---|
| author | Davide Garberi <dade.garberi@gmail.com> | Tue Sep 24 18:45:17 2019 +0200 |
| committer | Jackeagle <jackeagle102@gmail.com> | Sat Dec 12 07:24:07 2020 +0100 |
| tree | 3072ac57e52cf58ab93710c8530f7f5703884e8b | |
| parent | 5842f79b03a18f6a0802c484609ef3a38b99e219 [diff] |
releasetools: Move system mount handling to backuptool * This allows the ROM to be flashed on any recovery, whether it mounts system to /system, /system_root or /mnt/system like Q recovery * Remove any type of system mount with static paths from updater-script to figure out the path dinamically through backuptool Change-Id: I7b33726305cb6f3eec146d26135f0081002a25dc
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.