| commit | 96df304c6b01cc1a4ed8ac29137abd096e97345a | [log] [tgz] |
|---|---|---|
| author | Tom Powell <zifnab@zifnab06.net> | Fri Jan 20 20:47:49 2017 -0800 |
| committer | LuK1337 <priv.luk@gmail.com> | Sat Oct 19 00:16:01 2024 +0200 |
| tree | 27c4a118c309f3b0c415c5137aa6d0dcc6ff48d2 | |
| parent | 08f448e9cdf3f2fb5f30ea304a215e1106a3e020 [diff] |
releasetools: support reading release keys out of some sort of command key passphrases may live in some sort of secure storage, support running an arbitrary command to retrieve them. Change-Id: I49862cf60f1b73a2356e0c492e1038beef28a95f (cherry picked from commit 9caf8603575aecf51761feaeac6db619be76cfd3)
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.