commit | ecce5bc3f59f71d3016d0135feb47b9271c37903 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <[email protected]> | Thu Apr 04 16:30:10 2024 +0000 |
committer | Android Build Coastguard Worker <[email protected]> | Thu Apr 04 17:12:57 2024 +0000 |
tree | 47685532da30de698c892e3ed16724643d028654 | |
parent | b26493bfdfa65447bb4287b1ba46d8d3118e5696 [diff] | |
parent | 9515f9624d28af1f36fd15ab47ce75959a768d1a [diff] |
Make change and version bump to aml_res_341810000 for mainline module file: None Snap for 11670064 from 9515f9624d28af1f36fd15ab47ce75959a768d1a to mainline-resolv-release Change-Id: I8ee57e153c7efcb36e8fb8189c9526c7156274b0
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.