| commit | e3c31eac61e5a360ba6a06af46c062a3702a8d77 | [log] [tgz] |
|---|---|---|
| author | Tianjie <xunchang@google.com> | Tue May 19 13:44:26 2020 -0700 |
| committer | Tianjie <xunchang@google.com> | Mon Aug 17 18:38:13 2020 -0700 |
| tree | aaa1d24fa53e2527361245fe72e0bf257610b0fe | |
| parent | 14350c575f9e515502e1005f1834eec338069b8a [diff] |
Fix the syntax in install-recovery.sh We recently modify the logic in install-recovery.sh to support non-A/B updates on VAB launched devices. And the position of the $(getprop ro.boot.slot_suffix) is misplaced for the recovery image. For example: "if ! applypatch --check EMMC$(getprop ro.boot.slot_suffix):/dev/block/recovery:SHA1" should be: "if ! applypatch --check EMMC:/dev/block/recovery$(getprop ro.boot.slot_suffix):SHA1" Bug: 156979431 Test: rerun add_image_to_target_file, then validate_target_files Change-Id: Id2d45e281151a46d66b37ea8fdb7b5cb4ae72e81 (cherry picked from commit e55f62c971b01daa1565d0e93ef27368180d573f)
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.