| commit | 649311868c402c6de126730a99cfe90b438efee3 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Sun Jun 17 21:47:18 2018 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Tue Jun 19 09:26:58 2018 -0700 |
| tree | 60f7756ab7e1d3d8f5fe10ebd162096a5f945b4b | |
| parent | f16031cfecfe69b2e0964a9a703d2a3ac66541ae [diff] |
Fix vndk packaging to stop depending on phony targets These had been depending on the phony target for the library (liblz4.vendor), not the actual built file and notice file. Since we hadn't been saving the NOTICE file, and were only assuming the installed notice file path. save that away for use during packaging. Test: m vndk; diff out/target/product/generic/android-vndk-aosp_arm.zip Test: m vndk; diff out/target/product/generic_arm64/android-vndk-aosp_arm64.zip Change-Id: If9a4bed27030b7bd464cd3987739df94d32a0037
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.