| commit | 7f49a67d0d54c740300e9e1a20b0f17d4c2a91c5 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Thu Jan 27 18:15:53 2022 -0800 |
| committer | Colin Cross <ccross@android.com> | Fri Jan 28 16:56:43 2022 +0000 |
| tree | 8139094f2937c7b67f9332304555b9c1c2209670 | |
| parent | 90721770ca416329c59c20ebb9c1edcee9666f0f [diff] |
Add a keys argument to tapas Add a keys argument to tapas that allows specifying devkeys to use internal aosp_devkeys_* products that use the internal devkeys, which will allow building unbundled apps that use platform keys for testing. Bug: 216553104 Test: tapas CarMediaApp devkeys Change-Id: I2161be9e15f99713e11d22901d6eb7ad3c420093
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.