| commit | 37a1986454c67b031cb9b12e6427b31f8b49d0a1 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Wed Oct 31 16:31:46 2018 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Wed Oct 31 16:39:29 2018 -0700 |
| tree | 27752ace3ae0110b9f95ec4a093ec849d851dd16 | |
| parent | c66c317460514015c88005fa602e2774bc4989e3 [diff] |
De-dup INTERNAL_SYSTEMIMAGE_FILES to fix PDK builds On PDK builds, we sometimes end up with multiple entries in INTERNAL_SYSTEMIMAGE_FILES, if we've got the definition for it, and it's in PDK_FUSION_SYSIMG_FILES. This causes us to define multiple rules in sdk_font.mk, leading to overriding commands errors. Bug: 118634643 Test: attempt PDK build Change-Id: Ieb4f46c0eece96cf246197af4b03e693493cc6a1
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.