commit | 541f86efc445741dc845d3552b1b72498df51a58 | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Mon Aug 05 11:21:12 2019 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Mon Aug 05 11:21:12 2019 -0700 |
tree | 34bd2474b1c1a8bd24115b48c986eda92580a708 | |
parent | f9b1d54d7603feefb5455f0cf3eac798cf07bf95 [diff] | |
parent | dce8646ed973d4b4af42a167b024c5f03894cec5 [diff] |
Merge "Remove import_includes/export_includes" am: 6240872250 am: 0c5a068d02 am: baa4704f97 am: 823ab5d846 am: dce8646ed9 Change-Id: I8da292fe990c717cc78ce267048ef1fec059a9b6
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.