commit | fe3d2e672a527148f87c9739009d72a5f394e5ed | [log] [tgz] |
---|---|---|
author | Jordan Demeulenaere <jdemeulenaere@google.com> | Mon Feb 07 09:05:29 2022 +0000 |
committer | Jordan Demeulenaere <jdemeulenaere@google.com> | Mon Feb 07 09:05:29 2022 +0000 |
tree | 74e6af05f87cde36ece38c9ec2f5b68f515ceaaf | |
parent | c19c517894b7ff59a2652deebae3ed402e7eaf6b [diff] |
Revert "Add a core configuration that disables the zygote." Revert submission 1964759-master-I4f918502e611e950fa039e4e2ed817c97b928ba2 Reason for revert: b/217993447 Reverted Changes: I4f918502e:Add a core configuration that disables the zygote.... I4f918502e:Add a core configuration that disables the zygote.... I4f918502e:Add a core configuration that disables the zygote.... Change-Id: I5d51a021fea89a0ab6c73349d93117d60cfc9350
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.