| commit | 378b77929f12898c49a4adc18793cbfc620a4de3 | [log] [tgz] |
|---|---|---|
| author | Yi-Yo Chiang <yochiang@google.com> | Fri Apr 09 20:09:13 2021 +0800 |
| committer | Yo Chiang <yochiang@google.com> | Fri Apr 09 12:32:41 2021 +0000 |
| tree | c6d8dec4195a0c0e4ce9cbf76648ad2443e31124 | |
| parent | 90eeff54eaf49c7cc477f882dead82ecfbff8eed [diff] |
Strip whitespace from INTERNAL_VENDOR_RAMDISK_FRAGMENTS aosp/1664081 introduces a bug where if BOARD_VENDOR_RAMDISK_FRAGMENTS is empty, then INTERNAL_VENDOR_RAMDISK_FRAGMENTS would become " " (single whitespace). Just unconditionally $(strip ...) the variable to remove any extra whitespace. Bug: 183395459 Test: m dist and check *-target_files-*.zip Change-Id: Ic842756f3a64c073593592d22c980820664e11c1
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.