| commit | 133fcb2550c615ffa7772273de06b9e2ebb987a8 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Thu Jun 28 13:31:02 2018 +0100 |
| committer | Anton Hansson <hansson@google.com> | Mon Jul 09 13:17:52 2018 +0100 |
| tree | 71472efc6e449e75fba3c27239b7abdfa07065d3 | |
| parent | 88a60636b394274584c7da27e57ae2e218167a16 [diff] |
Warn when defining a 32-bit product on a 64-bit device. Building a 32-bit-app-only product on a 64-bit capable device is likely to be unintentional. Print a warning if this is done implicitly, e.g. via forgetting to define the TARGET_SUPPORTS_64_BIT_APPS variable. Also change existing references to only treat 'true' as a positive value, rather than all non-empty ones. Bug: 110918674 Test: lunched 64-bit-device product that does and doesn't set this var Change-Id: I021157c94ec3ac1c690547c8992768e58c89c287
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.