| commit | 8b162283f70b4f19d61c80a87ba34b0fc575f9c7 | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Mon Oct 30 16:22:53 2023 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Wed Nov 01 13:06:08 2023 +0900 |
| tree | f21e01031b22b5dc716a1dae14db777aed1c38c7 | |
| parent | da88660301cf8ae6412b2d58294c34a6753381c0 [diff] |
Rewrite how to generate apexkeys.txt Instead of listing all apexes in the source tree, now each apex emits its own fragment for apexkeys.txt, which is pointed by LOCAL_APEX_KEYS_FILE. Makefile collects apexkeys.txt from installed apex files. This is to avoid listing unrelated apexes (not installed, testdata, unexported namespaces, etc.) Bug: 304914238 Test: m apexkeys.txt Test: m blueprint-tests Change-Id: I6b5601609d16452a0717f09ecaa703ee09693094
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.