commit | 7b7cdb777728605a986b35b356a874bf066712de | [log] [tgz] |
---|---|---|
author | Alan Viverette <alanv@google.com> | Thu Mar 22 14:07:58 2018 -0400 |
committer | Colin Cross <ccross@android.com> | Thu May 03 16:47:11 2018 -0700 |
tree | 150935c193a060feaa7f14c0890a0ae496841601 | |
parent | fb8f5baae423a5ca952d4a47c788e1280bb118af [diff] |
Always statically include Support Libraries, move SDK definitions up a dir Bug: 73250914 Bug: 74248169 Test: make && make cts Change-Id: Id7198997ac5cacf76fd8ab155a60026d65e420ec Merged-In: Id7198997ac5cacf76fd8ab155a60026d65e420ec (cherry picked from commit 1efaf37cb7dda6807f66062ca6bf001f5066e4b4)
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.