| commit | f9fa82df2d2abcf540533d88b3e2c28abfc46512 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Jan 06 17:46:25 2023 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Jan 06 18:27:20 2023 +0000 |
| tree | eb643f4edde9e6cab145dc8dfc3b59bd61ac356e | |
| parent | 26bd4368c6e5c0a81c86660b62eae61a24bbd072 [diff] | |
| parent | 002198ece36d1dc4b05992b22070531ed0748a13 [diff] |
Make change and version bump to TKQ1.230106.001 Snap for 9459315 from 002198ece36d1dc4b05992b22070531ed0748a13 to t-keystone-qcom-release Change-Id: I9938c7847021799eae455804554a7a76855a3a75
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.