| commit | 44670e5fef268d891e528800fbaece3f2d7c270f | [log] [tgz] |
|---|---|---|
| author | Evgeny Eltsin <eaeltsin@google.com> | Mon Sep 23 12:06:22 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Mon Sep 23 12:06:22 2019 -0700 |
| tree | d8e033b3e43dc8ac3a75fc5d69effe55212f508a | |
| parent | 3a430830204ae77892c858b9057a1845eb006140 [diff] | |
| parent | 1adb3e1b89b964b860172383b76f89e546c3bb45 [diff] |
Merge "Add generic_x86_64_arm64 board" am: 0b58060cae am: 1adb3e1b89 Change-Id: Id9dcb7862f3ebe8fde02e629c1a859794724ed7a
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.