commit | c58f01b77e31ad2a8ead119275b6218c70613f43 | [log] [tgz] |
---|---|---|
author | Sam Delmerico <delmerico@google.com> | Thu Sep 01 13:38:00 2022 -0400 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue Sep 06 20:55:53 2022 +0000 |
tree | 4352f7408da1e735446c04cd14e6cab9e765180b | |
parent | 86c22c60b8c6692747ef4a903c6a76b0186902b0 [diff] |
add module_arm64only product 64bit only systems won't load modules with mixed 32/64 binaries. We need a 64bit only product to build with. Bug: 205990590 Test: lunch module_arm64only && m Change-Id: I050a673bfa95978e624e64004089fe7a2b8e0a95 (cherry picked from commit 01d7c4745acd050d63cd70b5d89f66ef5aa7cc9f) Merged-In: I050a673bfa95978e624e64004089fe7a2b8e0a95
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.