| commit | 6195b3578a4b4195c0d63602303907f417e7369a | [log] [tgz] |
|---|---|---|
| author | Tom Cherry <tomcherry@google.com> | Mon Oct 15 17:48:42 2018 -0700 |
| committer | Tom Cherry <tomcherry@google.com> | Tue Oct 16 09:58:54 2018 -0700 |
| tree | fbc86b7c756601fef7dd868b60a7f13d7c2810ed | |
| parent | 4e90c3f9a5243160ee893f3b2aa211a5e995cef9 [diff] |
Separate init packaging for mainline With system-as-root, both first and second stage init belong to system, but without system-as-root, first stage belongs to vendor and second stage belongs to system. This change references two phony packages that include the right parts of init for systen and vendor. Bug: 117606184 Test: mainline builds work properly Change-Id: I997309655fef28cb1c3d4b3be989c035b5c6488d
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.