commit | d33ccd069f316d9bb5fcdea30b1ec9f6b652d445 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed May 10 23:00:40 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu May 11 00:03:57 2023 +0000 |
tree | 0ea5dc08977760ab9f4a4350b6813762efb80760 | |
parent | 485a0f828bcd08df317e3ae1b55aac617e5e5b01 [diff] | |
parent | ad812265824f49664092ca7e4ec23005ac1cd212 [diff] |
Make change and version bump to UD1A.230511.001 Snap for 10107121 from ad812265824f49664092ca7e4ec23005ac1cd212 to udc-d1-release Change-Id: I2793d84d3440388be13d5041ffc939d5c584694e
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.