commit | c3e104f97f5c6ff4522b7b6dcba1b4e06ff394bf | [log] [tgz] |
---|---|---|
author | Joe Onorato <joeo@google.com> | Tue May 14 13:54:13 2024 -0700 |
committer | Joe Onorato <joeo@google.com> | Tue May 14 13:58:54 2024 -0700 |
tree | da72ed564cb7819f5427452ee6a939c48a551255 | |
parent | 666f85d0bce43f6a433b93efa387e7077cbd581a [diff] |
Provide a function in envsetup.sh to get the host arch directly It's very simple logic, and running get_build_var to do it is slow and has side effects (like needing a lunch target, creating an out directory, etc.) Test: source envsetup.sh Change-Id: If260efd21713874fba7c15dbc0fd23442d776f8a
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.