| commit | 95958eefa98eb0cb1d7defb9bc9d1923611c79ba | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Wed Feb 06 11:54:40 2019 +0000 |
| committer | Anton Hansson <hansson@google.com> | Thu Feb 07 13:06:18 2019 +0000 |
| tree | 7f6d95163f39efca5f8d84411234841060b64bb9 | |
| parent | 375291fa261f1c35df6e5296093834642cce03cf [diff] |
Change RRO default location to /product This changes the default location of RRO packages that don't specify where they should be installed to /product instead of /vendor. Also change the auto-generated "enforced RRO" packages to install on /product, and be explicit about that in the mk to make it independent of the RRO default. The reasoning for this change is that most overlays tend to be for product level customizations, like themes and so on. RROs for hardware related things can still be explicitly installed on /vendor. Bug: 123566903 Test: preubmit Test: various internal tests Change-Id: Ie7d5f19dc7ab421a7bcf584153f991e18e961cda
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.