commit | 18957187250fee3697e56e35fbfe44d7cde56cae | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sun Apr 09 21:01:11 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sun Apr 09 21:59:56 2023 +0000 |
tree | 06143c4768d4a8b98993a0e6439ebbdb6604fcf3 | |
parent | e95c6de90e416df4fbef101d3f2d286c45d9fa6c [diff] | |
parent | 1658acefc6fa3a8ecf5b5afeb273f0e113f3e984 [diff] |
Make change and version bump to TQ3A.230410.001 Snap for 9909434 from 1658acefc6fa3a8ecf5b5afeb273f0e113f3e984 to tm-qpr3-release Change-Id: Ic15331f8f96ba5ed2fb5209ff7d802aa8363a25f
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.