| commit | d6e239fc35474165e8d6133f462eda4411136fc9 | [log] [tgz] |
|---|---|---|
| author | Roshan Pius <rpius@google.com> | Fri Nov 22 08:47:40 2019 -0800 |
| committer | Roshan Pius <rpius@google.com> | Fri Nov 22 12:48:09 2019 -0800 |
| tree | 7d0afc605826a05bb05badf36af8eacc096d6f4f | |
| parent | 4a0832210cd529e999c4c150fa0874b1f568407e [diff] |
base_system.mk: Support system_server jars from apexes Allow system_server jars delivered via apex. Regular system_server jars are located in /system/framework folder. But, jars delivered via apex are mounted at /apex/<module_name>/javalib. Also, not all the libraries in /apex/<module_name>/javalib will be a system_server jar, so adding a mechanism to list out the jar file explicitly within the apex module. Bug: 144722612 Bug: 141785760 Test: Compiles (both with empty & non-empty PRODUCT_SYSTEM_SERVER_APEX_JARS value set) Change-Id: Ia181ab22fdf2da575bfd532c1cd90a2f54742528
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.