| commit | 0229ecfae50a470eff98eb8934694c18d78b7035 | [log] [tgz] |
|---|---|---|
| author | Greg Kaiser <gkaiser@google.com> | Thu Nov 09 20:28:55 2023 +0000 |
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Thu Nov 09 20:28:55 2023 +0000 |
| tree | e20995685ee9a91e4d0366aea75eef2a2f11c873 | |
| parent | 50fe46c1d3e588966d8bf800e1f4391c2523f22b [diff] |
Reland: Require TARGET_RELEASE for builds Relanding because we've fixed a number of the broken build setups this change exposed. We will push to fix forward broken build setups instead of reverting this change again. Rather than use an unsupported flag setting that the user likely doesn't even realize is being used, we immediately stop the build. This error message is more verbose, mentioning 'lunch', because it's anticipated a lot more users will hit this issue when first switching to trunk stable, and more details will hopefully help them out. We have some complication in that some internal commands set TARGET_RELEASE to an empty string. We put in logic to allow that path. Since $(error) immediately stops the build, we also get rid of some 'else' logic and indentation, to hopefully offset some of the complication we've added. Bug: 307946156 Change-Id: I0fa4a1c876e607401f4c7f945b9971cfb8db71a0 Test: 'lunch' (still) works; A build attempt without `TARGET_RELEASE` set (now) fails
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.