commit | 5c36806fbf0e2862385230829bb7b773c11b47d4 | [log] [tgz] |
---|---|---|
author | Evgeny Eltsin <eaeltsin@google.com> | Thu Sep 19 18:25:08 2019 +0200 |
committer | Evgeny Eltsin <eaeltsin@google.com> | Mon Sep 23 16:53:18 2019 +0200 |
tree | a22cd1e9095b8d68ff316e0a3b28e13844b84786 | |
parent | 08f9da189803ce9844c5dc7f8bbfb1d4b87e8a1e [diff] |
Add generic_x86_64_arm64 board An x86_64 board + third-party arm64 to x86_64 binary translator. Test: none Change-Id: I15c6249be8fc7f3e716213c9a3fe6b0fe9563d1c
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.