| commit | ab52f4baaa665d4dcda7cc433d4e7eb0697843a4 | [log] [tgz] |
|---|---|---|
| author | Islam Elbanna <islamelbanna@google.com> | Fri Nov 04 15:51:07 2022 +0000 |
| committer | Islam Elbanna <islamelbanna@google.com> | Fri Nov 04 15:52:37 2022 +0000 |
| tree | b7adc0f6d67e747129575cb4976afd14654e2b7f | |
| parent | 92716d2d594a465c904a4164a3e01f1ceb50ce30 [diff] |
Zip apex system server and standalone system server jars into system_server.zip. Currently, the Art benchmark service is depending on the boot.zip file to filter out boot image profiles based on the existing jars in this zip file, and to expand profiling to apex system server jars and standalone jars we need to export these jars in another zip file. Bug: 241823638 Test: Checked the generated `system_server.zip` using `m droidcore dist` Test: Checked with aosp and internal targets Change-Id: I477dcfd3381bd24bdc50aabb773b38f8840f0ce0
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.