commit | 3c214741008d9c14417938921e0be73778f223ac | [log] [tgz] |
---|---|---|
author | Rock.Yeh <rock.yeh@mediatek.com> | Wed Apr 22 17:01:10 2020 +0800 |
committer | Ulyana Trafimovich <skvadrik@google.com> | Mon Apr 27 08:21:22 2020 +0000 |
tree | b60339969898ee71328a442aece52c393d51f5f6 | |
parent | 198e9ae3731d35856218f3c2671ce347a58b37e0 [diff] |
Add PRODUCT_SYSTEM_SERVER_JARS_EXTRA interface This interface allows vendor to append their system server jars after AOSP's without changing inherit order. Test: booting Test: build pass on branch r-fs-release with this patch Bug: 140712566 Change-Id: I0ddf35bdf725c262f817985f5494b5968db21fcd Merged-In: I0ddf35bdf725c262f817985f5494b5968db21fcd (cherry picked from commit 2a703ce2f66d61595c3e492c5a27e1602913667c) Exempt-From-Owner-Approval: cherry-pick
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.