commit | 23c46cf42453bfef7f1bd88e21e422a75a281281 | [log] [tgz] |
---|---|---|
author | Roland Levillain <rpl@google.com> | Tue Mar 31 16:11:05 2020 +0100 |
committer | Roland Levillain <rpl@google.com> | Wed Apr 08 13:09:49 2020 +0100 |
tree | 9ed1a69106b61cdff8504196f6120fd55e8a2a6f | |
parent | 8459ede56d76e8f50ab8d3562e0460cab4dd72f1 [diff] |
Print a user-friendly message when `lunch` cannot use the default product. In some environments (e.g. with the master-art branch), the default product (aosp_arm-eng) cannot be built, and thus prevents `lunch` from printing the lunch menu (as it cannot initialize the build system in order to fetch the common lunch choices). When this happens, show an explicit error message from `lunch` instead of a Soong UI error. Test: Check that this command line displays the expected error message: unset TARGET_PRODUCT && . build/envsetup.sh && lunch Bug: 152762648 Change-Id: I40c66bca5b075d88dbc8364b36b2db713e6ad93e
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.