commit | 832f700223b68a62b87277567ebe58f790c65b53 | [log] [tgz] |
---|---|---|
author | Bowgo Tsai <bowgotsai@google.com> | Wed Sep 04 08:40:44 2019 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Wed Sep 04 08:40:44 2019 -0700 |
tree | 8e4d5cdc8fea2c4f6850a79caf4bc1441cd71429 | |
parent | 1c8b101c50560546f80e2516f405e6e4dfc83fef [diff] | |
parent | 3c3db483a1371a83dcf353db8f3bc21c2231648a [diff] |
Merge "Moving GSI-specific files to system_ext" am: a6c80c1117 am: 478bda0122 am: 3c3db483a1 Change-Id: I5d62bfb03a26881b2dd9e8d70987fd95a4cb5380
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.