commit | 7ddc50a066287b804a754951a597668d627478df | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Thu Oct 18 16:11:40 2018 -0700 |
committer | Dan Willemsen <dwillemsen@google.com> | Sat Oct 20 14:43:58 2018 -0700 |
tree | 1ba49bfc8ea468c13fabf973212353a006857559 | |
parent | 17c9e2a2960e8ef054593284c879d5a8d1d03fcf [diff] |
Refactor common makefile fragments In preparation for setting up another Kati stage, move some common settings and tools into a common folder. This way it's a bit easier to see that they're safe to use, and that they shouldn't depend on anything outside of the common folder. Bug: 117463001 Test: build-aosp_arm.ninja is the same before and after Change-Id: Ief4b75a4dbe45b73ffd03bf32c60695c816d979d
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.