| commit | 74dabedcb3ed045607e39ec1611191af2877ed89 | [log] [tgz] |
|---|---|---|
| author | Alyssa Ketpreechasawat <kalyssa@google.com> | Thu Feb 29 01:57:07 2024 +0000 |
| committer | Alyssa Ketpreechasawat <kalyssa@google.com> | Thu Feb 29 02:26:44 2024 +0000 |
| tree | 7460431bbabd123509eb40efe501e7ffc05f5427 | |
| parent | 0656d0a451703642fe13323ee340260f099676c2 [diff] |
Use build flag to control the apex boot jars to be excluded. Different prebuilts might have different contents and thus, different boot jars to be removed from the existing apex boot jar lists e.g. next using U prebuilts would need to remove framework-pdf while ap31 with V prebuilts must not remove such. The existing mechanism will always remove framework-pdf whenever prebuilts are enabled regardless of release config, which is not correct in context of multiple prebuilt support. Ignore-AOSP-First: for successful build, we need to submit this togther with ag/26332775. this cl will get cp'ed into aosp later on Bug: 327022391 Test: build device in next and trunk Merged-In: I9949fb7075ab6c207a292f13fd75e010a4958f87 Change-Id: I9949fb7075ab6c207a292f13fd75e010a4958f87
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.