| commit | 29770fa2bf8773d91fa4bc40b56b6330b3a0535f | [log] [tgz] |
|---|---|---|
| author | SzuWei Lin <szuweilin@google.com> | Thu Mar 28 11:46:48 2019 +0800 |
| committer | SzuWei Lin <szuweilin@google.com> | Thu Mar 28 13:41:01 2019 +0000 |
| tree | ae9832646cab205f267389a8aaa89314900388d4 | |
| parent | 5ed75d74e3906aee9ee174d81c1dd920f5b3f0c0 [diff] |
Fix build error on empty ramdisk package `init_vendor` is the only content of ramdisk so far. We would get build error if we do not include init_vendor. The patch fix the build error for the case that ramdisk is empty. Bug: 129386309 Test: lunch aosp_arm64_ab-userdebug; make ramdisk -j Test: Build pass Change-Id: I7c7c828b5f29350268d4789393b90740dd68162d
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.