| commit | 1578e23991e0f243315241d86e590478f62790c1 | [log] [tgz] |
|---|---|---|
| author | Bowgo Tsai <bowgotsai@google.com> | Wed Apr 24 15:33:03 2019 +0800 |
| committer | Bowgo Tsai <bowgotsai@google.com> | Wed Apr 24 09:01:49 2019 +0000 |
| tree | d9ecc03d64697a1053d26c07463ae5e4caf4e47f | |
| parent | 913478401a6c9718d4133f4cf7f28ba2d71a8b6c [diff] |
Fix build error for no-ramdisk targets In some build targets, e.g., aosp_arm64_ab, $OUT/ramdisk is an empty dir, and leads to rsync $OUT/ramdisk/* failure. Removing the trailing asterisk to avoid throwing an error if it's empty. Note that the trailing slash still needs to be kept to avoid creating an additional directory level at the destination. Bug: 126493225 Test: `make ramdisk_debug` on aosp_arm64_ab Test: flash boot-debug.img on crosshatch still can adb root Change-Id: I44937324379fa78fc26a4471ba94eb7694911c2d Merged-In: I44937324379fa78fc26a4471ba94eb7694911c2d
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.