| commit | 286874053c1fa1d24dd53bb6bda7fe4b03ee7971 | [log] [tgz] |
|---|---|---|
| author | cfig <yuyezhong@gmail.com> | Wed Aug 22 16:21:41 2018 +0800 |
| committer | Tao Bao <tbao@google.com> | Wed Aug 22 14:34:55 2018 -0700 |
| tree | 435fecb0ca8eed099f99c57d1d38123ddf964c1e | |
| parent | 0de30815ff51487fc2522845bcb72a8f8a0fc4ec [diff] |
use BOARD_PREBUILT_DTBOIMAGE in target-files-package
it's better to use the original $(BOARD_PREBUILT_DTBOIMAGE) instead
of AVB-padded $(INSTALLED_DTBOIMAGE_TARGET), the latter will be padded
to the size of /dtbo partition
Test: `make target-files-package` target file RECOVERY/recovery_dtbo is
the original BOARD_PREBUILT_DTBOIMAGE
Test: `make otapackage` build pass and OTA file works fine
Change-Id: Iec8524d3a0544ddca89481dc613f076b36aeed25
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.