commit | 25b2a651d5227ce4e87ffb860a336b7f6b554aa7 | [log] [tgz] |
---|---|---|
author | Christopher Ferris <cferris@google.com> | Wed Jul 13 22:58:40 2022 -0700 |
committer | Christopher Ferris <cferris@google.com> | Thu Jul 14 13:31:51 2022 -0700 |
tree | a8fe5ac6fe20093ece20b03d05da670665edeb77 | |
parent | aba99adea4cbc0ff0036e5523caebd3ff867daf7 [diff] |
Add ability to force compile as 64 bit. When trying to build a single 64 bit and 32 bit image, there are a few executables that are prefer32. When set, this will force all of those targets to be compiled as 64 bit. Test: With this option, drmserver/mediaserver are built as 64 bit. Test: Without this option, drmserver/mediaserver are built as 32 bit. Change-Id: I84f6be7fe0fa3a9ea86ecc4dd785aaf1825f9925
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.