| commit | a13cd28e4482576e5ac77c61f1ba6c5befa974f4 | [log] [tgz] |
|---|---|---|
| author | Greg Kaiser <gkaiser@google.com> | Wed Oct 25 16:17:40 2023 +0000 |
| committer | Greg Kaiser <gkaiser@google.com> | Wed Oct 25 16:18:45 2023 +0000 |
| tree | f3b91e8013c24e9f01fa161f58daa67fa91927fa | |
| parent | c87fd674a85b15446aa1ef8e6f68116d52bb2409 [diff] |
Have default 'lunch' target use a release type In git_main, the correct target here is aosp_arm-trunk_staging-eng (or "trunk_food" or "next", but we choose the most generic "trunk_staging"). Bug: 307738446 Test: "lunch", hit return for the default, "echo $TARGET_RELEASE" to confirm Change-Id: I4d4bcaf27553976e64133c7351db296953f88b08
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.