| commit | b952b5e4c3410feb527da12f0cf7bf5c81cee1c3 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Sat Feb 09 22:35:46 2019 -0800 |
| committer | Dan Willemsen <dwillemsen@google.com> | Wed Mar 06 15:41:19 2019 -0800 |
| tree | 41c8aedc04f203de7102309e2799bbbf44e3337f | |
| parent | 3d05a08a6fdd3537ec27258548fadea5994ffc2b [diff] |
Build everything in PRODUCT_HOST_PACKAGES This should only add extra host packages that were in PRODUCT_HOST_PACKAGES and not PRODUCT_PACKAGES. That shouldn't be very many things -- user builds will build a few more host tools that used to be in PRODUCT_PACKAGES_DEBUG, etc. Test: treehugger Change-Id: I6768b76db74ea049de90eef326d1e314eb4ef848 Merged-In: I6768b76db74ea049de90eef326d1e314eb4ef848
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.