| commit | 284b81c1aefc246e21623df5d0e25572bbba3a48 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Thu Oct 18 14:08:38 2018 +0100 |
| committer | Anton Hansson <hansson@google.com> | Mon Oct 29 16:15:04 2018 +0000 |
| tree | ac696331e5cf4244d569b09f7b16e9624651af04 | |
| parent | df45f28a82770c6083aaa3f94776382c0ac3d858 [diff] |
Add a mainline arm64 device The existing 'generic' targets are emulator devices, and targeting it has the side-effect of including emulator-specific artifacts. Create a mainline device instead, which is really generic. This also allows specifying tweaks unsuitable for the emulator. Include BoardConfigGsiCommon for now, even though it includes a few things we likely won't want in the future. Bug: 80410283 Bug: 111538404 Test: lunch mainline_arm64; m Change-Id: I15e7cb41fcbd3c0592a091ba7a8575ddf10bda71
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.