| commit | 169528bd8516b099cda29418dad6e823fa59f081 | [log] [tgz] |
|---|---|---|
| author | Magnus Strandh <magnus1.strandh@sony.com> | Tue Dec 17 23:08:12 2024 +0100 |
| committer | Håkan Kvist <hakan.kvist@sony.com> | Thu Dec 19 12:16:54 2024 +0100 |
| tree | 0e9764d74ef9fa69a3364a89926b4d577a62b04e | |
| parent | b0b317ff3c1294a42a8629815858c2fa04e7c3e0 [diff] |
Extend merge_ota with extra options for signapk.jar Add the same parameters for supporting custom signapk.jar to merge_ota as already supported by ota_from_targetfiles introduced in: a28acc6972ce35e9dfab061f175e229859d3e4db This makes it possible for an oem to use a custom signapk.jar for the package signing when using merge_ota. Bug: 384969259 Test: local Change-Id: Ia2713f5b0007d6aee34d9546396d744fb5fe6943
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.