commit | 304da757b9dd874cbc98f313aa4579c9cc1381e5 | [log] [tgz] |
---|---|---|
author | David Anderson <dvander@google.com> | Sat Oct 09 04:17:52 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Sat Oct 09 04:17:52 2021 +0000 |
tree | 1828cf9da928f3df9cb173a3c79c873951c09a19 | |
parent | e2f39ac6cc08d860c2647a55e8db1563105ad4fc [diff] | |
parent | c31d965bfadd361f9c2d017c1c8a1a664a7738b9 [diff] |
Merge "Clean up code duplication in build_image.py." am: 514ec3b59a am: 1fd5a857e9 am: 88369ad70d am: d540a6b9fe am: c31d965bfa Original change: https://android-review.googlesource.com/c/platform/build/+/1835298 Change-Id: I3db289d2bb69f3b68045d1e2e7c693dfbb4813e8
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.