| commit | 44ffb21e53d051d95a05c9c09fb3f9bfd4358004 | [log] [tgz] |
|---|---|---|
| author | Jiakai Zhang <jiakaiz@google.com> | Thu Oct 28 14:37:20 2021 +0000 |
| committer | Jiakai Zhang <jiakaiz@google.com> | Tue Nov 30 11:07:37 2021 +0000 |
| tree | 3f054d59ff7eeab5c346cc6e1ac5699ad2ed012b | |
| parent | d373dd29385364dae161943f53ea4262cdeb51ce [diff] |
Add a variable to specify standalone system server jars. This is the list of jars that system_server loads dynamically using separate classloaders. We will rely on this variable to decide which jars to preopt in the build system and on the device for system_server. The list is supposed to be in sync with the code in SystemServer.java. There will be a follow-up CL to add a comment in SystemServer.java to remind developers to keep them in sync. Bug: 203198541 Test: m nothing Change-Id: I305a73218ef2d2c61ac3795d21026b2afe7007fd
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.