| commit | 32fb8e31115e53a8aa6dc5e94fd2a3b331c3e763 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Mon Oct 07 12:46:27 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Mon Oct 07 12:46:27 2019 -0700 |
| tree | 6c31bac09425c9c76cb24acdf15d453be6d9038f | |
| parent | 208eeb88cb5c17ec0c55356d2d4e1031e2e9bf0a [diff] | |
| parent | 85e79118fd608da60b3537299ce63fa82af5ca73 [diff] |
Merge "releasetools: Fix releasetools_py3_test." am: ae3a9a138d am: fa4ea59837 am: 4bdfb36549 am: 85e79118fd Change-Id: I10e137b745b7a8924b1001d59c29ee147caf43ae
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.