| commit | bae4c57b7b3144aa094417330ff977813aa14e21 | [log] [tgz] |
|---|---|---|
| author | Greg Kaiser <gkaiser@google.com> | Thu Jan 04 15:57:54 2024 -0700 |
| committer | Greg Kaiser <gkaiser@google.com> | Thu Jan 04 16:36:07 2024 -0700 |
| tree | f94a5343a205672d9e6c68d36934e90e653e5f46 | |
| parent | 04591b6315b64c3d3805a6ee874bd11abd3851f3 [diff] |
Change default lunch target
We keep this as "trunk_staging" and "eng". However, we switch
from "aosp_arm" to "aosp_cf_x86_64_phone". This switches us
away from 32-bit development, and gives us a project (the
cuttlefish ("cf") emulator) at the end of the build which is
runnable with reasonable performance, and able to run all 32-bit
and 64-bit tests.
Bug: 318749634
Test: lunch
Change-Id: I920cdd413cbcecd4300bc46c719e5788244a924e
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.