| commit | 17063cfcb0735e6d2abf7f34296e8da5d0f6db02 | [log] [tgz] |
|---|---|---|
| author | David Anderson <dvander@google.com> | Fri Aug 27 16:43:09 2021 -0700 |
| committer | David Anderson <dvander@google.com> | Fri Aug 27 16:50:30 2021 -0700 |
| tree | 134379a5861447ccb9fca2ae0c661f75e7fbbbf5 | |
| parent | f72c0facd35dc29d71d9c8e5d25cc42cca2389e1 [diff] |
Fix generate-userimage-prop-dictionary getting called unnecessarily. odm, odm_dlkm, vendor_dlkm call generate-userimage-prop-dictionary. This appears to be inadvertent as it pulls in props from all the other partitions. Instead, call generate-image-prop-dictionary which is specific to one partition. Bug: 198001223 Test: builds, treehugger green Change-Id: Ib177c740068f1c087d517b363649551092038760
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.