| commit | f0601c094ab801a148891d30f2fbeb33deb15094 | [log] [tgz] |
|---|---|---|
| author | Ian Kasprzak <iankaz@google.com> | Wed Oct 02 12:54:21 2024 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Oct 02 18:16:26 2024 +0000 |
| tree | e02e0385adbb099ac4b1599cb5095794027d2bf1 | |
| parent | 32a7ed576994b4138e4590376acf410c9bb40827 [diff] |
Move ap3a configuration to build/release. Bug: 349843674 Bug: 370829778 Ignore-AOSP-First: "Migrating AP3A to build/release" (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:4ff90549123b218377c7d576282614a3d3b35be1) Merged-In: Ie339d505c73b297e05f764c2c27cc525923fa225 Change-Id: Ie339d505c73b297e05f764c2c27cc525923fa225
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.