| commit | 9b7c1e4393b1d1f6af95a650b4e162dfcf3f0899 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Mon Nov 05 10:40:45 2018 -0800 |
| committer | Dan Willemsen <dwillemsen@google.com> | Mon Nov 05 10:57:24 2018 -0800 |
| tree | 0e5d97023001bc08d0a4ef03ddf2829bf0673fa7 | |
| parent | 4c9399d9889ee07a933fe3053d34ee6420e45442 [diff] |
Fix pre-extracted PDKs The PDK unzip logic does not place all the files in the same directory it would place a zipfile, but instead inside a directory of the same name: a/b/platform.zip!pdk.mk turns into: a/b/platform/pdk.mk So fix the PDK_FUISON_PLATFORM_DIR autodetection to take this into account. Also don't create touch rules for the pre-extracted java files. Bug: 118776469 Test: try building the PDK with PDK_FUSION_PLATFORM_ZIP set, and files extracted Change-Id: Ib27d12aba773a5e6bd41fcbe8945a0bc31b8c281
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.