tequilaOS/platform_build
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
platform_build/target/product/base_system.mk

409 lines
9 KiB
Makefile
Raw Normal View History

Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
#
Split base.mk into system and vendor parts. Put all packages that end up on the vendor partition in a separate mk, to allow creating products with artifact path requirements. Bug: 80410283 Test: diff product vars with multiproduct_kati Change-Id: Ia35adaed2c8f9989c180bfdbbeeb2a5ecf634aa5
2018-06-25 14:35:01 +02:00
# Copyright (C) 2018 The Android Open Source Project
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
Split base.mk into system and vendor parts. Put all packages that end up on the vendor partition in a separate mk, to allow creating products with artifact path requirements. Bug: 80410283 Test: diff product vars with multiproduct_kati Change-Id: Ia35adaed2c8f9989c180bfdbbeeb2a5ecf634aa5
2018-06-25 14:35:01 +02:00
# Base modules and settings for the system partition.
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
PRODUCT_PACKAGES += \
Rename adbd_system_binaries to adbd_system_api. This is going to include libraries as well, so rename to reflect this. Bug: http://b/157709367 Test: treehugger Change-Id: I94625a6343e18032d8607cf8c58bde49d64db85c
2020-06-02 03:57:25 +02:00
adbd_system_api \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
am \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
android.hidl.allocator@1.0-service \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
android.hidl.base-V1.0-java \
android.hidl.manager-V1.0-java \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
android.hidl.memory@1.0-impl \
android.hidl.memory@1.0-impl.vendor \
Add android.system.suspend@1.0-service to base_system.mk Bug: 78888165 Test: presubmit Change-Id: I644ebc0704749dbbb7840563d237736babcb003a
2018-08-30 05:35:11 +02:00
android.system.suspend@1.0-service \
Conditionally remove atb from bootclasspath If REMOVE_ATB_FROM_BCP=true then this adds the framework-atb-backward-compatibility library to the bootclasspath. Otherwise, it adds the android.test.base library instead. Bug: 30188076 Test: build, flash and test manually and with FrameworkCoreTests Change-Id: I3c15c35724426a9cdeef398c5bc4f5176a8fc752
2018-01-24 17:41:33 +01:00
android.test.base \
Added android.test.mock to PRODUCT_PACKAGES Adds android.test.mock.jar to the /system/framework directory. That will allow it to be dynamically included with a uses-library manifest entry. Bug: 30188076 Test: flash and check contents of /system/framework Change-Id: I3ea0e558276176edd21e24c8337980c5c02a652e
2017-06-05 16:46:00 +02:00
android.test.mock \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
android.test.runner \
Add ANGLE.apk to the base system This CL re-enables building ANGLE as parta of the base system. This was done up until the recent merge of goog/master to aosp/master, and is required as part of enabling ANGLE as the default OpenGL ES driver for Cuttlefish. Bug: b/168625635 Test: atest CtsAngleIntegrationHostTestCases Change-Id: I12c8db290ed7dc6b213b6f1c22692666dcdf143f Merged-In: Ide4e3d8f78d3748d557a47ecd153d66694fd1e3a
2020-09-17 22:21:28 +02:00
ANGLE \
Add apexd to base_system. apexd is a new daemon responsible for managing APEX packages. Bug: 112455435 Test: apexd is running Change-Id: I097495af4a6f7374b4d40da4512e3faf517520a1
2018-08-17 13:46:58 +02:00
apexd \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
appops \
app_process \
appwidget \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
atrace \
Add audioserver executable to base config Bug: 24511453 Change-Id: Ic6575fc8f5a4ab1a75854dc488021d7d06fa1e97
2015-10-29 02:03:50 +01:00
audioserver \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
BackupRestoreConfirmation \
bcc \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
blank_screen \
Add blkid to all builds for use by vold. vold now uses blkid to extract UUID and label information from inserted physical devices. Bug: 11175082 Change-Id: I56ebe733ff85a498f6d3cbdcf21d40ddc6123f82
2013-10-17 00:42:51 +02:00
blkid \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
bmgr \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
bootanimation \
bootstat \
Add boringssl_self_test to base PRODUCT_PACKAGES. When building from source this gets installed as a requirement from Conscrypt, but needs to be present when Conscrypt is shipped as a pre-built too. I think the correct solution here is actually to make libcrypto rather than Conscrypt require boringssl_self_test but Soong considers that a circular dependency. Bug: 155520949 Test: m installclean && m Change-Id: I77b2921d1d7b6be493cd581c46adbadd1f186fb0
2020-05-07 15:11:34 +02:00
boringssl_self_test \
Add bpfloader binary to system image The bpfloader is a executable binary used by netd to load and attach networking related bpf program at run time. It need to be flashed to device when updating the system image. Currently this binary is only used by devices with kernel version 4.9 or above. Test: hikey boot and bpf program show up under sys/fs/bpf Bug: 30950746 Change-Id: I3d14d270a04ea57319ad4292ff51b1cf933fc975
2018-02-10 00:17:22 +01:00
bpfloader \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
bu \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
bugreport \
Added bugreportz binary. BUG: 28479946 Change-Id: Ic0d1b6598867ccbbc65f3fdc0d32cac7c53128a3
2016-05-02 20:18:07 +02:00
bugreportz \
Add cgroups.json and task_profiles.json build targets Add cgroups.json and task_profiles.json into the list of packages. Bug: 111307099 Test: builds, boots Change-Id: Ib8ab11de573505f522ccd9cec2c6afd7e23d2f2f Signed-off-by: Suren Baghdasaryan <surenb@google.com>
2018-12-14 18:31:52 +01:00
cgroups.json \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
charger \
cmd \
Build the adbd apex. Test: adb shell "su 0 readlink /proc/\`pidof adbd\`/exe" Change-Id: I29227a79765fca8f0f2601f0fefa6f01232fbc6f
2019-09-30 19:58:36 +02:00
com.android.adbd \
Add Conscrypt APEX to base image Test: manual inspection of base image Bug: 110404540 Change-Id: Ief4104ab0a2b42407554b96e9a8b1b47cddff156
2018-12-11 14:27:01 +01:00
com.android.conscrypt \
Revert "DO NOT MERGE: Delete com.android.cronet from base_system. am: 8640960329" This reverts commit 14199b7a933491f83dfed72ef8c6b84ce3e4a449. Reason for revert: Rollback the stuff which has been removed due to "remove cronet for R" to keep the intermediate branches synced between {aosp, internal} master Bug: 156368607 Change-Id: I95bcb80ccd330ce7f40a20912ab61c1ff9d15441 Merged-In: Ice9b733b22d45d6d6eaf8e3f3ed95b3ac50eefbb
2020-05-15 07:35:43 +02:00
com.android.cronet \
Move ExtServices in com.android.ext apex. Bug: 147674123 Test: built on aosp_taimen and verified package is available from the apex. Change-Id: I59c070cf9b4ea6afef590888849de96ead84fde2
2020-01-17 03:16:15 +01:00
com.android.extservices \
Add com.android.i18n APEX module to PRODUCT_PACKAGES Bug: 137009149 Test: device boots Change-Id: I9de4e6930456e52dec76dd2a67d6e7ddad393332
2019-07-05 18:33:05 +02:00
com.android.i18n \
Add com.android.ipsec APEX to base makefile com.android.ipsec will be shipped as a mainline module in APEX format Bug: 143905344 Test: Built and installed apex on device Change-Id: I70da069146e8d9a7be38ab603c6bdaa9d6d9ba84
2019-11-05 00:22:57 +01:00
com.android.ipsec \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
com.android.location.provider \
Add com.android.media in the default build. Test: make systemimage on sailfish and marlin Bug: 112766425 Change-Id: I05678f08dac0e5dbc29e80ee8025a9b5e39f0102
2018-12-06 20:18:44 +01:00
com.android.media \
media: move com.android.media.swcodecs to base_system.mk. This can now be supported on all devices. Bug: 129710438 Change-Id: Ide0921361ce6b22655f6f5a2695fc892dbe47998 (cherry picked from commit 4609a369d4b97ea86245b311c438dc005cfca168)
2019-04-03 00:28:35 +02:00
com.android.media.swcodec \
Structure MediaProvider as an APEX. Based on guidance from the Mainline team, we're placing the MediaProvider APK inside a new APEX, as this will allow us to move MediaStore.java inside the module boundary in a future CL. As part of this restructuring, we need the pre-Mainline APK to remain intact to preserve the user's media database. There is already logic in place from previous CLs that will migrate data from the pre-Mainline to the post-Mainline world, including tests to verify that the migration works. Bug: 144247087 Test: atest --test-mapping packages/providers/MediaProvider Change-Id: I571eccbb2950a7c518a682eae3350ba7ef9bd804
2019-11-21 23:57:09 +01:00
com.android.mediaprovider \
Add statsd apex to base_system Bug: 145960929 Test: atest statsd_e2e_tests --rebuild-module-info Change-Id: I83476ea471abbf5803a1edc3cb717ee450e6e152
2019-12-11 03:51:48 +01:00
com.android.os.statsd \
Add permission APEX to base_system. Bug: 136503238 Test: atest --rebuild-module-info permission_e2e_tests Change-Id: Id2a01c2c4660627380c6f2b39eef800683502837
2019-11-12 22:05:14 +01:00
com.android.permission \
Add the dns resolv module to /system This includes the dns resolv APEX in the system image Bug: 119527674 Test: build / boot crosshatch Change-Id: Ie92db9979fb63bfabcd29590d0ea236fd8717970
2018-11-27 04:23:27 +01:00
com.android.resolv \
Move libneuralnetworks.so to com.android.neuralnetworks APEX Test: build&flashed crosshatch image Bug: 137320025 Change-Id: Iadbb32cffc636c515a5e89b62539183ebc0c2f14
2019-07-12 15:04:43 +02:00
com.android.neuralnetworks \
Add framework-statsd.jar to jars list Add framework-statsd.jar to product_boot_jars and product_updatable_boot_jars Bug: 145923096 Test: m Test: vendor/google/tools/flashall Test: adb shell cmd stats print logs && adb logcat "*:S statsd:*" Change-Id: I00e9cfa847554e745bd7c18dffda13e9f7ab4130
2019-12-12 02:54:05 +01:00
com.android.sdkext \
[Tether16] Build Tethering package Create com.android.tethering apex to pack Tethering.apk and framework-tethering.jar together. For go devices, tethering would run in system server process by InProcessTethering.apk Bug: 144320246 Test: -build, boot Change-Id: Id2d68117e99173682908168e99ee28670bd71871
2019-11-20 12:46:00 +01:00
com.android.tethering \
Add the time zone data module to /system This includes the time zone data APEX in the system image which should flush out any obvious issues. Bug: 119026403 Test: build / boot taimen Change-Id: I3d9a8289d8af405a373c94891b482540e59a3571
2018-11-07 19:54:26 +01:00
com.android.tzdata \
base_system.mk: Switch to wifi mainline apex Also, explicitly include the cacerts_wfa in builds. This used to be included via the "required" tag in wifi-service build rule. We probably don't want to deliver CA certificates to OEM devices via mainline updates. So, leaving it out of the wifi mainline module & explicitly including it in the base makefile. Bug: 144722612 Test: Device boots up & connects to wifi networks. Change-Id: I3e4487f9fad765e442bf8335ec1f21de3a47674d
2019-11-23 02:11:36 +01:00
com.android.wifi \
Delete core_tiny.mk Only inherited by a single mk, so inline its contents there, with a few exceptions: - pppd was redundant (already in base) - ContactsProvider and DefaultContainerService were duped in base.mk's only two children (core_tiny and core_minimal) Bug: 80410283 Test: diff product variables with multiproduct_kati Change-Id: I95431b3db789e9c347bb37109a3ac7f627025f96
2018-06-19 14:48:51 +02:00
ContactsProvider \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
content \
Use APK CtsShim prebuilts for flattened apex. Fix: 158036322 Test: built flame-userdebug with m OVERRIDE_TARGET_FLATTEN_APEX=true, ran atest CtsAppSecurityHostTestCases:android.appsecurity.cts.PrivilegedUpdateTests#testDisableUpdatedSystemApp and verified that the cts shim apex is not installed Change-Id: Icc52500cfc0a555e11d1a467b2da0649c7f5d31f Merged-In: Icc52500cfc0a555e11d1a467b2da0649c7f5d31f (cherry picked from commit c9a786e5f77a5c06da6c07f718e4a7619a75d9e6)
2020-06-04 11:42:42 +02:00
CtsShimPrebuilt \
CtsShimPrivPrebuilt \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
debuggerd\
Add device_config module for debugging configuration flags. Test: check installed files on local builds. Bug:109919982 Bug:113101834 Change-Id: Ie9ae3930f216efe932dcc6246bbf9cc6e3b8ff14
2018-11-20 19:30:58 +01:00
device_config \
Add 'dmctl' to default debug utilities. dmctl can list all device mapper targets and their tables which is extremely useful information for a bugreport. Especially to compare the device mapper setup with the partition metadata. Bug: 120916687 Test: 'dmctl list device -v' Change-Id: I9e3afcf146b2814b0304f69cdf6029303beb57c7 Signed-off-by: Sandeep Patil <sspatil@google.com>
2018-12-18 18:47:27 +01:00
dmctl \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
dnsmasq \
Move a few packages from core_minimal.mk to base.mk. All the products that inherit from base.mk add these packages, so moving them up the hierarchy eliminates some duplication. DownloadProvider idmap libneuralnetworks mdnsd MediaProvider Bug: 80410283 Test: diff all product variables with multiproduct_kati Change-Id: I133a385b3bc64261d73f616c416f7a905675c09d
2018-06-14 17:23:57 +02:00
DownloadProvider \
Added new 'adb dpm' command to the packages list. Bug: 17312478, 17316711 Change-Id: I2613178ea82a6c6268e7f8012e74c4a852fea0d4
2014-09-11 18:52:08 +02:00
dpm \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
dumpstate \
dumpsys \
Rename module DynamicAndroidInstallationService Rename this module to DynamicSystemInstallationService per one of the API review suggestions. Bug: 126613281 Test: build, install, and check the module is there Change-Id: I2b1d2ba787c8d76f770ede23e90b4e09f7e4c143
2019-03-07 07:36:31 +01:00
DynamicSystemInstallationService \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
e2fsck \
ExtShared \
add flags_health_check binary to system_base.mk Test: build succeeded, /system/bin/flags_health_check can be found on device Change-Id: Ia8b73d7bbfc6951e580f62b6bebf006211b0ce33
2018-10-27 04:20:46 +02:00
flags_health_check \
Replace framework.jar with framework-minus-apex.jar Bug: 139391334 Test: m, device is bootable Change-Id: I281f841c164a4813ed4c436fb84680f5ade1ee1d
2019-10-21 07:34:35 +02:00
framework-minus-apex \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
framework-res \
Add framework sysconfig content to the build Bug 30953212 Change-Id: I2f9f301a38c9d2e7214222f00a44f8ef23f36e6f
2017-01-13 22:54:21 +01:00
framework-sysconfig.xml \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
fsck_msdos \
Add fsverity release cert The release cert helps verifying CTS in a release build. Bug: 153112812 Test: build, reboot, see a new key in /proc/keys Change-Id: I6d8f4af6b1b0c023b668e81b7a1c71c7583d93d9
2020-04-04 00:04:09 +02:00
fsverity-release-cert-der \
Split up fs_config_* modules per partition. This was already done for partitions other than the system partition. Add new, separate "_system" targets, and add new phony modules which collects _system and _nonsystem targets for now. Update the base_system.mk file to only depend on the system module, and put the other ones in base_vendor.mk for now. Bug: 80410283 Test: make fs_config_dirs[_*] fs_config_files[_*] and verify output Change-Id: I7843578dbb9f27edf4c1e5b4a795a530f79e0be1
2018-06-26 15:03:38 +02:00
fs_config_files_system \
fs_config_dirs_system \
Generate /etc/{passwd,group} for all partitions Bug: 73062966 Test: can load AIDs from partitions other than vendor Test: bionic-unit-tests Merged-In: Ia85abbeefe5a945369970f2aef42692e07ab8c09 Change-Id: Ia85abbeefe5a945369970f2aef42692e07ab8c09 (cherry picked from commit 8a54ec8482cc7bfa892fe1749f53b4c1a17f026e)
2019-07-12 00:31:36 +02:00
group_system \
Add gsid The gsid is a daemon for managing GSI. Bug: 122556707 Test: make && ls ${OUT}/bin/gsid Change-Id: Ib4a3e95a7e232236ee1255a156043e45a77a3c8e
2019-01-15 08:54:48 +01:00
gsid \
Add gsi_tool and DynamicAndroidInstallationService to base_system Bug: 122015653 Test: run "adb shell am ..." to trigger DynamicAndroidInstallationService full command: adb shell am start-activity -a android.content.action.START_INSTALL -e KEY_SYSTEM_URL <file_url> --el KEY_SYSTEM_SIZE <system_image_size> --el KEY_USERDATA_SIZE 8589934592 Test: run "adb shell gsi_tool" Change-Id: I4045a16dd50066c8a303be13c524ed4c09f60f87
2019-01-24 12:20:58 +01:00
gsi_tool \
Build heapprofd per default. See go/heapprofd for details. This will be used to profile the memory usage of system services and apps. See https://b.corp.google.com/issues/111289182#comment2 for system health approval. Change-Id: I2cf3af57e22c39c968afc0ca971f1d3862e27fe2
2018-10-15 15:09:08 +02:00
heapprofd \
heapprofd_client \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
gatekeeperd \
[GPU Service] Add gpuservice into PRODUCT_PACKAGES. BUG: 118347356 Test: Build, flash, boot, `adb shell cmd gpu vkjson` to verify Change-Id: Ib9a7d13817853da040c8c4059beca90418de4621
2018-11-01 21:38:25 +01:00
gpuservice \
Add hid command to base build Bug: 21662862 Change-Id: I11ed67b8f0efd1232ddfbb6e0a5f4bdbb065397e
2015-06-24 16:55:21 +02:00
hid \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
hwservicemanager \
Add modules 'idmap2', 'idmap2d' Test: builds, boots Change-Id: I1d806dc875a493e730ab55d2fdb027618e586d16
2018-07-13 15:47:39 +02:00
idmap2 \
idmap2d \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
ime \
Revert submission 1182953-1576003954286-8455af5a Reason for revert: Crashes telephony process when saving XML config from carrier apps (b/146727232) Reverted Changes: Ieaeec41f1: Whitelist telephony-common, ims-common. I5588f7615: Add telephony-common, ims-common to telephony apex... I81e922c0d: Add telephony-common, ims-common to telephony apex... Change-Id: Ia64b73682fcc77db63e220867c66c4319c417582
2019-12-26 22:42:49 +01:00
ims-common \
Add incident (protobuf bugerport / known bad) files to base.mk product. Test: make -j32 Change-Id: I3a1fd4bfa44af02a5a384e24a669f50c3310ef46
2016-11-21 08:21:25 +01:00
incident \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
incidentd \
Add incident_helper to base build Test: NA Change-Id: Idb567ad2a84977d7fd4eb1ebf3bfb24a157664f3
2017-07-31 20:51:16 +02:00
incident_helper \
Add incident-helper-cmd build target Add a Java binary util target incident-helper-cmd. See frameworks/base addition (ag/10054587) for details. Test: build Bug: 146086597 Change-Id: Ifd202d8622e32fbd9644930cdae4d0546ce5d481
2020-01-14 00:16:18 +01:00
incident-helper-cmd \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
init.environ.rc \
Separate init packaging for mainline With system-as-root, both first and second stage init belong to system, but without system-as-root, first stage belongs to vendor and second stage belongs to system. This change references two phony packages that include the right parts of init for systen and vendor. Bug: 117606184 Test: mainline builds work properly Change-Id: I997309655fef28cb1c3d4b3be989c035b5c6488d
2018-10-16 02:48:42 +02:00
init_system \
Fix embedded build 1) Disable dexpreopt if DALVIK_VM_LIB isn't set up by the product. 2) DEX2OAT_TARGET_INSTRUCTION_SET_FEATURES is moved to config.mk, for it's only decided by target arch. 3) Move Java module input from embedded.mk to base.mk. Change-Id: Ife70b0cd8cee2e5c92f356c808affa56f494b49a
2014-03-20 20:13:10 +01:00
input \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
installd \
base_system: Add iorapd as core product target This makes iorapd be built as part of the system image with a regular 'make' command. Part of a topic that has 'iorapd' start up by init_rc. Bug: 72170747 Change-Id: I300bc35f508fbe36bf0f545e20236c718392d571
2018-10-06 01:28:12 +02:00
iorapd \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
ip \
iptables \
ip-up-vpn \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
javax.obex \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
keystore \
Add keystore2 to PLATFORM_PACKAGES Add keystore 2 to the PLATFORM_PACKAGES in anticipation for the Keystore 2.0 migration. This builds and installs keystore2 on the device, but it does not get started yet. Staring keystore2 is currently controlled with the platform property ro.android.security.keystore2.enable=true. Bug: 171305684 Test: keystore2 builds and is present on the device but does not start unconditionally. Change-Id: Id92cb2aa38022516067853d89d6c3210db1100a8
2020-09-11 18:47:45 +02:00
keystore2 \
Identity: Add credstore In order to support mDL on RVC, we need to add credstore in /system/bin Bug: 136506289 Test: atest VtsHalIdentityTargetTest Change-Id: I7975eddde5b94edcd3a2d0e213244f84ffe43e8d
2020-06-04 12:46:05 +02:00
credstore \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
ld.mc \
libaaudio \
libamidi \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
libandroid \
Move 6 packages up from core_base.mk Also remove two nonexistant packages (libnfc_ndef & libvariablespeed). The moved packages are already being pulled in by being required by other included packages in one of its parents (base or core_minimal). These are the moved packages and their pre-existing deps: - libmdnssd: by netd in base.mk - libandroidfw: by 7 packages, many in base.mk - libaudioutils: by 3 packages, e.g libmedia in base.mk - libpowermanager: by 3 packages, e.g. libaudioflinger in base.mk - libspeexresampler: by libaudioutils - libwebrtc_audio_preprocessing: by libaudiopreprocessing in core_minimal.mk This change makes core_base.mk very small. It will be deleted in a followup-CL and its contents inlined in its direct children. Bug: 80410283 Bug: 7456955 Test: make Change-Id: I1240ec6adc5b9208effd6fc70892dfbd453a1fba
2018-06-26 11:51:58 +02:00
libandroidfw \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
libandroid_runtime \
libandroid_servers \
Add libartpalette-system Test: ssh to mac, lunch, build, flash, boot device. Change-Id: Iddeb6b7e69edbf260be1148428fd9aa468d4559d
2019-02-20 14:35:31 +01:00
libartpalette-system \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
libaudioeffect_jni \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
libbinder \
Install libbinder_ndk to the system. This library is in the NDK, so it needs to be guaranteed to be installed even thought there are no platform dependencies on it. Bug: 111445392 Test: it is installed Change-Id: Iba7b224f0d95c62634a728ce7e178af6d08aa7dc
2018-08-30 05:52:48 +02:00
libbinder_ndk \
Install bootstrap variant of bionic libs Bionic libs are moved to the runtime APEX and thus are available via the path /apex/com.android.runtime/lib[64]. However, for processes that are started before the APEX is ready, a copy of the bionic libs should be left under /system/lib[64]. This change ensures that the bootstrap bionic libs are always installed to the system partition. Note that, at runtime, the bionic libs in the runtime APEX are bind-mounted to /system/lib/<libname>.so which essentially hides the bootstrap bionic libs to the processes after the activation of the runtime APEX. Bug: 120266448 Test: m and check that libc, libdl, libm are under /system/lib[64] Change-Id: I9d5e8e718aa020c012f312a70ed54652130048dd
2018-12-26 09:32:56 +01:00
libc.bootstrap \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
libcamera2ndk \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
libcutils \
Install bootstrap variant of bionic libs Bionic libs are moved to the runtime APEX and thus are available via the path /apex/com.android.runtime/lib[64]. However, for processes that are started before the APEX is ready, a copy of the bionic libs should be left under /system/lib[64]. This change ensures that the bootstrap bionic libs are always installed to the system partition. Note that, at runtime, the bionic libs in the runtime APEX are bind-mounted to /system/lib/<libname>.so which essentially hides the bootstrap bionic libs to the processes after the activation of the runtime APEX. Bug: 120266448 Test: m and check that libc, libdl, libm are under /system/lib[64] Change-Id: I9d5e8e718aa020c012f312a70ed54652130048dd
2018-12-26 09:32:56 +01:00
libdl.bootstrap \
Reland "Add libdl_android as a bootstrap library". Necessary after moving it into the Runtime APEX, as several framework libraries loaded during early boot depends on it, e.g. libvndksupport.so, libvulkan.so, and libgraphicsenv.so. Test: build & boot Bug: 135753770 Bug: 144343305 Change-Id: Ia95349e377605d709fae74d966bd4f2324eaf604
2019-11-11 16:33:32 +01:00
libdl_android.bootstrap \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
libdrmframework \
libdrmframework_jni \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
libEGL \
libETC1 \
Add libfdtrack to base_system. Bug: http://b/140703823 Test: manual Change-Id: I6015946b85a4564b82eb57a0a0a9bb1e058b100a
2020-01-02 21:44:52 +01:00
libfdtrack \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
libFFTEm \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
libfilterfw \
libgatekeeper \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
libGLESv1_CM \
libGLESv2 \
libGLESv3 \
libgui \
libhardware \
libhardware_legacy \
Add inputflinger to build. Change-Id: I4ae22cda74603c7cdcf09b9f63b31616b1f8e345
2013-07-13 01:52:38 +02:00
libinput \
libinputflinger \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
libiprouteutil \
libjnigraphics \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
libjpeg \
liblog \
Install bootstrap variant of bionic libs Bionic libs are moved to the runtime APEX and thus are available via the path /apex/com.android.runtime/lib[64]. However, for processes that are started before the APEX is ready, a copy of the bionic libs should be left under /system/lib[64]. This change ensures that the bootstrap bionic libs are always installed to the system partition. Note that, at runtime, the bionic libs in the runtime APEX are bind-mounted to /system/lib/<libname>.so which essentially hides the bootstrap bionic libs to the processes after the activation of the runtime APEX. Bug: 120266448 Test: m and check that libc, libdl, libm are under /system/lib[64] Change-Id: I9d5e8e718aa020c012f312a70ed54652130048dd
2018-12-26 09:32:56 +01:00
libm.bootstrap \
Move 6 packages up from core_base.mk Also remove two nonexistant packages (libnfc_ndef & libvariablespeed). The moved packages are already being pulled in by being required by other included packages in one of its parents (base or core_minimal). These are the moved packages and their pre-existing deps: - libmdnssd: by netd in base.mk - libandroidfw: by 7 packages, many in base.mk - libaudioutils: by 3 packages, e.g libmedia in base.mk - libpowermanager: by 3 packages, e.g. libaudioflinger in base.mk - libspeexresampler: by libaudioutils - libwebrtc_audio_preprocessing: by libaudiopreprocessing in core_minimal.mk This change makes core_base.mk very small. It will be deleted in a followup-CL and its contents inlined in its direct children. Bug: 80410283 Bug: 7456955 Test: make Change-Id: I1240ec6adc5b9208effd6fc70892dfbd453a1fba
2018-06-26 11:51:58 +02:00
libmdnssd \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
libmedia \
libmedia_jni \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
libmediandk \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
libmtp \
Introduce netd_client, a dynamic library that talks to netd. (cherry picked from commit 440de6b9f715cb18b8ee888c58d5c7a659ff5073) Change-Id: Ib6198e19dbc306521a26fcecfdf6e8424d163fc9
2014-05-12 20:51:29 +02:00
libnetd_client \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
libnetlink \
libnetutils \
Add libneuralnetworks_packageinfo to dependencies. libbinder communication from APEX is not allowed, because it doesn't form a stable way to communicate. After an update, if system libbinder and APEX libbinder are out of sync, then they may fail to work with each other. libbiner usage is moved into libneuralnetworks_packageinfo library, which is a stable API library. Test: build & flash crosshatch Bug: 139282353 Change-Id: I7238025af13e9430c266a1aea69f0d0381110df8
2019-09-12 14:23:34 +02:00
libneuralnetworks_packageinfo \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
libOpenMAXAL \
libOpenSLES \
Revert "Fix build: Revert "Switching to the final PDF rendering library"" This reverts commit fa4f6471c48d2255a08432b20b0b16f3ae712d4c. Change-Id: I7541ddad1302ca0f39aec62e3c4ca399046e56a6
2014-05-21 21:40:31 +02:00
libpdfium \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
libpower \
Move 6 packages up from core_base.mk Also remove two nonexistant packages (libnfc_ndef & libvariablespeed). The moved packages are already being pulled in by being required by other included packages in one of its parents (base or core_minimal). These are the moved packages and their pre-existing deps: - libmdnssd: by netd in base.mk - libandroidfw: by 7 packages, many in base.mk - libaudioutils: by 3 packages, e.g libmedia in base.mk - libpowermanager: by 3 packages, e.g. libaudioflinger in base.mk - libspeexresampler: by libaudioutils - libwebrtc_audio_preprocessing: by libaudiopreprocessing in core_minimal.mk This change makes core_base.mk very small. It will be deleted in a followup-CL and its contents inlined in its direct children. Bug: 80410283 Bug: 7456955 Test: make Change-Id: I1240ec6adc5b9208effd6fc70892dfbd453a1fba
2018-06-26 11:51:58 +02:00
libpowermanager \
added broadcast radio service Added core libraries for broacast radio service, client and meta data utility. Change-Id: Ic93444aee9a41c02dce67c8170450ac111332a62
2015-02-14 03:22:22 +01:00
libradio_metadata \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
librtp_jni \
libsensorservice \
media: move com.android.media.swcodecs to base_system.mk. This can now be supported on all devices. Bug: 129710438 Change-Id: Ide0921361ce6b22655f6f5a2695fc892dbe47998 (cherry picked from commit 4609a369d4b97ea86245b311c438dc005cfca168)
2019-04-03 00:28:35 +02:00
libsfplugin_ccodec \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
libskia \
Adding libsonic to base.mk Adding Sonic library to base bug: 19196501 Change-Id: Id39a3a2f843aadf2808a10d2017151461db2c9b2
2015-04-11 00:43:30 +02:00
libsonic \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
libsonivox \
libsoundpool \
Move 6 packages up from core_base.mk Also remove two nonexistant packages (libnfc_ndef & libvariablespeed). The moved packages are already being pulled in by being required by other included packages in one of its parents (base or core_minimal). These are the moved packages and their pre-existing deps: - libmdnssd: by netd in base.mk - libandroidfw: by 7 packages, many in base.mk - libaudioutils: by 3 packages, e.g libmedia in base.mk - libpowermanager: by 3 packages, e.g. libaudioflinger in base.mk - libspeexresampler: by libaudioutils - libwebrtc_audio_preprocessing: by libaudiopreprocessing in core_minimal.mk This change makes core_base.mk very small. It will be deleted in a followup-CL and its contents inlined in its direct children. Bug: 80410283 Bug: 7456955 Test: make Change-Id: I1240ec6adc5b9208effd6fc70892dfbd453a1fba
2018-06-26 11:51:58 +02:00
libspeexresampler \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
libsqlite \
libstagefright \
libstagefright_foundation \
libstagefright_omx \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
libstdc++ \
libsurfaceflinger \
libsysutils \
libui \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
libusbhost \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
libutils \
Add libvulkan to base PRODUCT_PACKAGES Change-Id: Ie0d583a349a6ef5542da91e5c1f1f348f02fe435
2016-01-27 09:20:35 +01:00
libvulkan \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
libwilhelm \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
linker \
Add Linkerconfig to base system target Add Linkerconfig to base system target Bug: 135004088 Test: m -j & Tested from device Change-Id: I02a3b58854c2f19866f42ba22541737c132daa44
2019-06-26 09:38:17 +02:00
linkerconfig \
llkd: moved from optional to required component The Live Lock Killer Daemon (llkd) has provided enough hero moments to improve system stability, by providing actionable collection of data to resolve kernel, and some user space, misbehaviors. It is time to move llkd to a required component. NB: For llkd to be effective at finding real kernel live lock conditions, system requirements are that there are no more un-waited for Zombie processes, and that no kernel drivers use indeterminate periods of uninterruptible sleep. Any kernel and user space tasks that are killed because of suspicious behavior, must themselves have a benefactor to restart them if necessary. If a true live lock is discovered, data will be collected and the kernel will be panic'd to recover from the situation. Signed-off-by: Mark Salyzyn <salyzyn@google.com> Bug: 164946924 Test: llkd is ever present on a release build. Change-Id: I986a8545252bc5b68d09a6a0f4f506a58998c8a0
2020-09-08 16:49:55 +02:00
llkd \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
lmkd \
Move transport out of system server. Test: manual, gts,cts. Bug: 113569323 Change-Id: I22834cbe076038439b8af88675206d9203a421c3
2018-08-30 14:41:14 +02:00
LocalTransport \
Add missing locksettings package Change-Id: Icf50402a5adc8b007ee3c27dcf0e4ccc65c35425 Fixes: 33430858 Fixes: 33645392
2016-12-16 01:50:36 +01:00
locksettings \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
logcat \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
logd \
Add lpdump to all builds Right now, it takes 29K. Test: builds Change-Id: I8f2e4be52cca6697724988ddc880aa6f29166cd1
2018-12-19 20:30:10 +01:00
lpdump \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
lshal \
Move a few packages from core_minimal.mk to base.mk. All the products that inherit from base.mk add these packages, so moving them up the hierarchy eliminates some duplication. DownloadProvider idmap libneuralnetworks mdnsd MediaProvider Bug: 80410283 Test: diff all product variables with multiproduct_kati Change-Id: I133a385b3bc64261d73f616c416f7a905675c09d
2018-06-14 17:23:57 +02:00
mdnsd \
Add mediacodec.policy to the mainline system. Bug: 110363419 Bug: 116668460 Test: make -j Change-Id: I557f99fe463435a78c6b803b08b944574319f0a9
2019-01-17 19:24:21 +01:00
mediacodec.policy \
Add extractorservice executable to base config Change-Id: I0ffbe183decfd76be681e08b8627c3d789c4b916
2015-09-26 00:02:06 +02:00
mediaextractor \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
mediametrics \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
media_profiles_V1_0.dtd \
Structure MediaProvider as an APEX. Based on guidance from the Mainline team, we're placing the MediaProvider APK inside a new APEX, as this will allow us to move MediaStore.java inside the module boundary in a future CL. As part of this restructuring, we need the pre-Mainline APK to remain intact to preserve the user's media database. There is already logic in place from previous CLs that will migrate data from the pre-Mainline to the post-Mainline world, including tests to verify that the migration works. Bug: 144247087 Test: atest --test-mapping packages/providers/MediaProvider Change-Id: I571eccbb2950a7c518a682eae3350ba7ef9bd804
2019-11-21 23:57:09 +01:00
MediaProviderLegacy \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
mediaserver \
mke2fs \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
monkey \
mtpd \
ndc \
netd \
Revert "Revert "Use NetworkStackNext as preinstalled network stack"" This reverts commit a60d3c0dc1b87c1cfebfc9b42488e2147a6bd21a. Reason for revert: Roll forward after fixing tests in b/144168912 Change-Id: Ibe68f086f10bbef7590ac4b721be4e1709e154dc
2019-11-11 04:53:01 +01:00
NetworkStackNext \
Add on-device signing binary to base. Bug: 165630556 Test: inspect image Change-Id: Ia428165be4a9800df23918330ab027458c84836d
2020-11-27 12:22:46 +01:00
odsign \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
org.apache.http.legacy \
Build otacerts as a module. Bug: 30414428 Test: `m -j dist` with aosp_taimen-userdebug. Check /system/etc/security/otacerts.zip available under system and recovery images. Change-Id: I5abeb2da441fb3e3231e094063c2383eb3807852 (cherry picked from commit b7936f3d2e16bcad36dcbfc72123381726dbc3c5)
2019-04-19 03:37:32 +02:00
otacerts \
Split PackageInstaller app into installation and permissions management The two components were mostly independant for a long time. Since I1e80a3f5e63d02b3859ecf74af21ca4c61f96874 the installation flow does not grant any permissions anymore and the last connection between these parts was broken. The new app "com.android.packageinstaller" in frameworks/base/packages/PackageInstaller will only handle (side load) package installtion and uninstallation. The exisiting app will be renamed to "com.android.permissioncontroller" and only handle permission granting and permission management. This change set also updates the make files to install the two apps on the appropriate devices. Test: Installed + uninstalled packages Change-Id: I37dda69218ea2a703a6379bb5bcbd3449b3360ad
2018-07-27 18:16:15 +02:00
PackageInstaller \
Generate /etc/{passwd,group} for all partitions Bug: 73062966 Test: can load AIDs from partitions other than vendor Test: bionic-unit-tests Merged-In: Ia85abbeefe5a945369970f2aef42692e07ab8c09 Change-Id: Ia85abbeefe5a945369970f2aef42692e07ab8c09 (cherry picked from commit 8a54ec8482cc7bfa892fe1749f53b4c1a17f026e)
2019-07-12 00:31:36 +02:00
passwd_system \
Add perfetto daemons and cmdline client to core makefiles Perfetto is a tracing daemon that allows both to capture traces from the kernel (via the traced_probes binary) and allows data to be pushed from userspace (via the traced binary). Tracing is never enabled by default and can be kicked off either via statsd or by the shell. The daemon executables are split only for the sake of security and isolating SELinux domains. Under the hoods they are just two shells that run code in the same shared libarary. See go/perfetto-sys-health-details for expected binary / memory / overhead impact. Bug: 72484603 Test: builds (see go/perfetto-test-spec for test plan) Change-Id: Ib5fbd7cd2113010398802b622363b75f3eef738d
2018-01-25 13:08:04 +01:00
perfetto \
Revert "Remove ping." This reverts commit 68007028fd6a8a27ff1bee05679862ebc7dc9051 Change-Id: I07ff0d756dff12472633e535c51a29b9062cc3fc
2013-02-22 20:37:38 +01:00
ping \
Include ping6 in all device builds ping6 is currently only included in debug builds. Include it everywhere, now that it doesn't need to be setuid any more. Bug: 9469682 Change-Id: Ia78f6b0e5fc8f7042fb99cdb4a0add426bb56c7e
2013-07-11 05:54:05 +02:00
ping6 \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
platform.xml \
pm \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
pppd \
Add package whitelist for user types Adds a sysconfig xml file for whitelisting system packages to install on user depending on their user type. Test: see the sister cl (ag/9154475) Bug: 134605778 Change-Id: Iacb16645c6416c8651ced5e9863d8f3628fca247
2019-08-07 23:48:35 +02:00
preinstalled-packages-platform.xml \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
privapp-permissions-platform.xml \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
racoon \
Add recovery-persist to base_system We moved the recovery metric parsing to the native code, which executes on the next normal build and stays under the system partition. Also, the recovery-persist binary needs to be installed on both A/B and non-A/B devices. Therefore, adds recovery-persist to base_system to avoid breaking the mainline targets. Bug: 114278989 Test: build mainline target Change-Id: I251ef862d9342b0dc308223ee6c48849f098bb1e
2018-09-20 21:31:33 +02:00
recovery-persist \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
resize2fs \
Add rss_hmw_reset to system partition rss_hwm_reset is binary that reset RSS high-water mark counters for all currently running processes. It runs in a separate process because it needs dac_override capability. The binary is not a persistent service. It is invoked from a system service by flipping sys.rss_hwm_reset.on property. Bug: 119603799 Test: adb shell ls /system/bin Change-Id: Iee0b54ec6486d8f23048819493f6d710db3feff6
2018-11-15 13:58:37 +01:00
rss_hwm_reset \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
run-as \
Add libraries txt file to build target Linkerconfig requires more libraries txt files to get library list related variable values. To make this available from runtime, those should be added as build target and included in system image. Bug: 137511540 Test: m -j && tested from cuttlefish Change-Id: I713c4419e4ed52e22561a5988f6c233ecce91c9d
2019-07-23 10:47:15 +02:00
sanitizer.libraries.txt \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
schedtest \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
screencap \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
sdcard \
Build "secdiscard" for securely discarding data from flash devices. Bug: 19706593 Change-Id: I073b7b39f25b054abdf2b983a63d029d690970a9
2015-06-04 10:59:33 +02:00
secdiscard \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
SecureElement \
Include partition-split selinux_policy modules. The selinux_policy module has been split in two, so that the system artifacts can be included separately. Also remove associated whitelist entries. Bug: 80410283 Test: for t in eng userdebug user; do lunch mainline_arm64-${t}; m nothing; done Change-Id: Id704c907b1ed31ae49697d33f075c013bc3dfc8c
2018-07-02 15:36:28 +02:00
selinux_policy_system \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
sensorservice \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
service \
servicemanager \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
services \
Add the new 'settings' shell tool to the build The tool isn't useful unless it's actually built into products. Bug 7299066 Change-Id: I9aaf37bde73a986d871eac6fd4dea15c192110cb
2012-10-10 23:13:59 +02:00
settings \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
SettingsProvider \
Include sgdisk in all device builds. sgdisk is the command line version of gptfdisk, which we're using to format devices with the GUID partition table standard. Change-Id: I99e0c56d35391d46031d1c2f04956332e1a164a9
2015-02-23 19:06:56 +01:00
sgdisk \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
Shell \
Split base.mk into system and vendor parts. Put all packages that end up on the vendor partition in a separate mk, to allow creating products with artifact path requirements. Bug: 80410283 Test: diff product vars with multiproduct_kati Change-Id: Ia35adaed2c8f9989c180bfdbbeeb2a5ecf634aa5
2018-06-25 14:35:01 +02:00
shell_and_utilities_system \
New "sm" shell tool to call StorageManager. Bug: 19993667 Change-Id: I9021794eb6f69c7f53151a887a85788d315ab67d
2015-05-13 00:53:29 +02:00
sm \
Add snapshotctl to base system Test: build and check output Bug: 135752105 Change-Id: I229fd03994e7145b9e05452c4d564379c53d8a61
2019-09-18 01:16:41 +02:00
snapshotctl \
Add snapuserd to VABC product and base_system.mk. Bug: 168259959 Test: builds Change-Id: I289f84e293c84b12f5f33f8940643bac43ff5d35
2020-10-17 00:07:03 +02:00
snapuserd \
Migrate ringtone picking out of MediaProvider. Some OEMs have requested the ability to customize the ringtone picker logic, and that's already supported by the existing "config_defaultRingtonePickerEnabled" parameter today. This change is a clean refactoring of the AOSP ringtone picker out of MediaProvider and into a new "SoundPicker" module, which is consistent with how some OEMs have already defined their own "SoundPickerPrebuilt" module. Bug: 134542205 Test: atest --test-mapping packages/providers/MediaProvider Change-Id: I3460b3a264859280c23e1a804b1d1bb1e99af329
2019-08-21 22:38:11 +02:00
SoundPicker \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
storaged \
surfaceflinger \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
svc \
Add cgroups.json and task_profiles.json build targets Add cgroups.json and task_profiles.json into the list of packages. Bug: 111307099 Test: builds, boots Change-Id: Ib8ab11de573505f522ccd9cec2c6afd7e23d2f2f Signed-off-by: Suren Baghdasaryan <surenb@google.com>
2018-12-14 18:31:52 +01:00
task_profiles.json \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
tc \
Add 'adb shell telecom' command to packages list Change-Id: I193b54dd9f4511eb7959c5dbbf38f90267b8fcc9
2015-06-03 22:57:33 +02:00
telecom \
Revert submission 1182953-1576003954286-8455af5a Reason for revert: Crashes telephony process when saving XML config from carrier apps (b/146727232) Reverted Changes: Ieaeec41f1: Whitelist telephony-common, ims-common. I5588f7615: Add telephony-common, ims-common to telephony apex... I81e922c0d: Add telephony-common, ims-common to telephony apex... Change-Id: Ia64b73682fcc77db63e220867c66c4319c417582
2019-12-26 22:42:49 +01:00
telephony-common \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
tombstoned \
Add perfetto daemons and cmdline client to core makefiles Perfetto is a tracing daemon that allows both to capture traces from the kernel (via the traced_probes binary) and allows data to be pushed from userspace (via the traced binary). Tracing is never enabled by default and can be kicked off either via statsd or by the shell. The daemon executables are split only for the sake of security and isolating SELinux domains. Under the hoods they are just two shells that run code in the same shared libarary. See go/perfetto-sys-health-details for expected binary / memory / overhead impact. Bug: 72484603 Test: builds (see go/perfetto-test-spec for test plan) Change-Id: Ib5fbd7cd2113010398802b622363b75f3eef738d
2018-01-25 13:08:04 +01:00
traced \
traced_probes \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
tune2fs \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
tzdatacheck \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
uiautomator \
uncrypt \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
usbd \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
vdc \
Add viewcompiler to device This is needed so that we can generate precompiled layouts at app install time. Bug: 111895153 Change-Id: Ia2905fdcecc1517e6ae2c8dd4317e3a41ebee107
2019-01-11 23:14:11 +01:00
viewcompiler \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
voip-common \
Make the base product depend on webview indirectly. Instead of depending on libwebcore directly as part of the base product, depend on the phony "webview" target from frameworks/webview instead, to allow the Chromium-powered webview to override it. Change-Id: I2f9c103a57a730b252e8a05d52c5b4c1b9711319
2012-10-31 18:10:36 +01:00
vold \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
WallpaperBackup \
Include watchdogd where init is included watchdogd is now separated out from init, so include it where init is included. Bug: 73660730 Test: watchdogd is still included on builds Change-Id: I8208b4bcfd4e2a948744c241b744daf0be3d1381
2018-08-01 22:45:12 +02:00
watchdogd \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
wificond \
base_system.mk: Package wifi.rc separately into the build These contain a bunch of action triggers for setting some kernel flags for wifi driver logging. Apex'es don't support .rc with action triggers, so package it separately into the build. Bug: 149909892 Test: Device boots up and connects to wifi networks. Test: Manually verified that the .rc file is run on bootup. Change-Id: I05f055ec68d47a1d158135f5454389a786884f9b
2020-02-20 16:51:02 +01:00
wifi.rc \
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
wm \
move device_manifest.xml to base_vendor.mk Test: make Change-Id: I500269591065569f3102d025b222517dfd4e2c84
2018-07-11 01:43:19 +02:00
# VINTF data for system image
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
PRODUCT_PACKAGES += \
Add product manifest. - Rename framework_manifest.xml to system_manifest.xml since that's more accurate. - Add product_manifest.xml to base_product.mk - Add product_manifest.xml to verified_assembled_framework_manifest.xml to check it at build time. Bug: 126770403 Bug: 130714844 Bug: 80547152 Test: build and inspect output Test: lshal Change-Id: I1b447d8c36f72768e28e9bcaa4d06afdeba08c2a
2019-04-24 02:09:07 +02:00
system_manifest.xml \
Add product_compatibitility_matrix.xml to base_product. The module refers to framework compatibitlity matrix that defined OEM modules. Also, renamed framework_compatibility_matrix.xml to system_compatibility_matrix.xml, since framework_compatibility_matrix.xml consists of both system and product compatibility matrices. This fixes mainline build. Test: build Test: boot device with product compatibility matrix Bug: 120600021 Change-Id: Ibfb12578c3ec77b6baede4eed852074e08022119
2019-01-23 00:49:53 +01:00
system_compatibility_matrix.xml \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
Manually install hwasan runtime on SANITIZE_TARGET=hwaddress builds Due to bugs in Soong around prebuilt libraries with stubs versions, the hwasan runtime was installed into /system/lib64/bootstrap, but the module was not given a ".bootstrap" suffix. Once the bugs are fixed, the hwasan runtime is no longer installed because the dependencies on "libclang_rt.hwasan-aarch64-android" are now on an uninstallable stubs library. Add libclang_rt.hwasan-aarch64-android.bootstrap to PRODUCT_PACKAGES when SANITIZE_TARGET=hwaddress is set. Test: m checkbuild Change-Id: I732d37505274c7bf804396921202f2bcca4484ec
2020-09-24 21:47:50 +02:00
# HWASAN runtime for SANITIZE_TARGET=hwaddress builds
ifneq (,$(filter hwaddress,$(SANITIZE_TARGET)))
PRODUCT_PACKAGES += \
libclang_rt.hwasan-aarch64-android.bootstrap
endif
Move jacocoagent installation to base_system jacocoagent and its dependencies emits artifacts to system/, hence it belongs to base_system.mk. It was rather incorrect to add jacocoagent to EVERY product makefile because those product makefiles may be enforcing artifact path requirements (e.g. generic_ramdisk.mk). Test: EMMA_INSTRUMENT=true m nothing Bug: 175605139 Bug: 173742069 Change-Id: If9cb93ab8fd69d11e764ab830dc791bbe6106cf5
2020-12-16 18:49:18 +01:00
# Jacoco agent JARS to be built and installed, if any.
ifeq ($(EMMA_INSTRUMENT),true)
ifneq ($(EMMA_INSTRUMENT_STATIC),true)
# For instrumented build, if Jacoco is not being included statically
# in instrumented packages then include Jacoco classes into the
# bootclasspath.
PRODUCT_PACKAGES += jacocoagent
PRODUCT_BOOT_JARS += jacocoagent
endif # EMMA_INSTRUMENT_STATIC
endif # EMMA_INSTRUMENT
Reland "First pass at creating PRODUCT_HOST_PACKAGES" Adds icu-data_host_runtime_apex to fix unbundled builds which pull it in via PRODUCT_PACKAGES, but are missing packages that would pull it in via PRODUCT_HOST_PACKAGES. Test: build/soong/build_test.bash Test: in ub-timezonedata-master; tapas TimeZoneData; m Change-Id: I1583c7582b386c3e8478711cb1df340518d763c1
2019-02-23 00:06:03 +01:00
# Host tools to install
PRODUCT_HOST_PACKAGES += \
BugReport \
adb \
Add art-tools to host build outputs Building of host tools stopped when moving to APEX. This change re-enables building of host tools. Bug: 128990084 Test: m -j72 && find out -name 'oatdump' Change-Id: Iad42b4e36561001709634174014192e56a64aafd
2019-03-25 14:36:59 +01:00
art-tools \
Reland "First pass at creating PRODUCT_HOST_PACKAGES" Adds icu-data_host_runtime_apex to fix unbundled builds which pull it in via PRODUCT_PACKAGES, but are missing packages that would pull it in via PRODUCT_HOST_PACKAGES. Test: build/soong/build_test.bash Test: in ub-timezonedata-master; tapas TimeZoneData; m Change-Id: I1583c7582b386c3e8478711cb1df340518d763c1
2019-02-23 00:06:03 +01:00
atest \
bcc \
bit \
e2fsck \
fastboot \
flags_health_check \
Add com.android.i18n APEX module to PRODUCT_PACKAGES Bug: 137009149 Test: device boots Change-Id: I9de4e6930456e52dec76dd2a67d6e7ddad393332
2019-07-05 18:33:05 +02:00
icu-data_host_i18n_apex \
Add a host simulation of the tzdata module Sets up additional files so that host environments can now have a simulation of the time zone data mainline module in addition to the simulation of the runtime mainline module they already have. Bug: 132169989 Test: Treehugger only Change-Id: I43dadb150e359bbcb9da61e0187286ac6d38f7c2
2019-06-05 14:54:18 +02:00
icu_tzdata.dat_host_tzdata_apex \
Reland "First pass at creating PRODUCT_HOST_PACKAGES" Adds icu-data_host_runtime_apex to fix unbundled builds which pull it in via PRODUCT_PACKAGES, but are missing packages that would pull it in via PRODUCT_HOST_PACKAGES. Test: build/soong/build_test.bash Test: in ub-timezonedata-master; tapas TimeZoneData; m Change-Id: I1583c7582b386c3e8478711cb1df340518d763c1
2019-02-23 00:06:03 +01:00
idmap2 \
incident_report \
ld.mc \
lpdump \
mdnsd \
minigzip \
mke2fs \
resize2fs \
sgdisk \
sqlite3 \
tinyplay \
tune2fs \
tzdatacheck \
unwind_info \
unwind_reg_info \
unwind_symbols \
viewcompiler \
tzdata_host \
Add a host simulation of the tzdata module Sets up additional files so that host environments can now have a simulation of the time zone data mainline module in addition to the simulation of the runtime mainline module they already have. Bug: 132169989 Test: Treehugger only Change-Id: I43dadb150e359bbcb9da61e0187286ac6d38f7c2
2019-06-05 14:54:18 +02:00
tzdata_host_tzdata_apex \
tzlookup.xml_host_tzdata_apex \
Reland "First pass at creating PRODUCT_HOST_PACKAGES" Adds icu-data_host_runtime_apex to fix unbundled builds which pull it in via PRODUCT_PACKAGES, but are missing packages that would pull it in via PRODUCT_HOST_PACKAGES. Test: build/soong/build_test.bash Test: in ub-timezonedata-master; tapas TimeZoneData; m Change-Id: I1583c7582b386c3e8478711cb1df340518d763c1
2019-02-23 00:06:03 +01:00
tz_version_host \
Add a host simulation of the tzdata module Sets up additional files so that host environments can now have a simulation of the time zone data mainline module in addition to the simulation of the runtime mainline module they already have. Bug: 132169989 Test: Treehugger only Change-Id: I43dadb150e359bbcb9da61e0187286ac6d38f7c2
2019-06-05 14:54:18 +02:00
tz_version_host_tzdata_apex \
Reland "First pass at creating PRODUCT_HOST_PACKAGES" Adds icu-data_host_runtime_apex to fix unbundled builds which pull it in via PRODUCT_PACKAGES, but are missing packages that would pull it in via PRODUCT_HOST_PACKAGES. Test: build/soong/build_test.bash Test: in ub-timezonedata-master; tapas TimeZoneData; m Change-Id: I1583c7582b386c3e8478711cb1df340518d763c1
2019-02-23 00:06:03 +01:00
Add new "wm" command. Change-Id: I2415b7696b1d310233a5202b42df5f80f02f4b9f
2013-02-16 01:35:35 +01:00
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
PRODUCT_COPY_FILES += \
Move init and ueventd scripts from / to /system/etc There is no reason for these scripts to continue to exist in /, when they are better suited for /system/etc. There are problems keeping them at / as well, particularly that they cannot be updated with overlayfs. Bug: 131087886 Bug: 140313207 Test: build/boot Merged-In: I5aa0332e7f0e3fb6840b60e3d099c2b28d38b7ea Change-Id: I5aa0332e7f0e3fb6840b60e3d099c2b28d38b7ea
2019-11-04 19:41:51 +01:00
system/core/rootdir/init.usb.rc:system/etc/init/hw/init.usb.rc \
system/core/rootdir/init.usb.configfs.rc:system/etc/init/hw/init.usb.configfs.rc \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
system/core/rootdir/etc/hosts:system/etc/hosts
Move init and ueventd scripts from / to /system/etc There is no reason for these scripts to continue to exist in /, when they are better suited for /system/etc. There are problems keeping them at / as well, particularly that they cannot be updated with overlayfs. Bug: 131087886 Bug: 140313207 Test: build/boot Merged-In: I5aa0332e7f0e3fb6840b60e3d099c2b28d38b7ea Change-Id: I5aa0332e7f0e3fb6840b60e3d099c2b28d38b7ea
2019-11-04 19:41:51 +01:00
PRODUCT_COPY_FILES += system/core/rootdir/init.zygote32.rc:system/etc/init/hw/init.zygote32.rc
Move ro.zygote to vendor The system property ro.zygote should be define in vendor. It went to system wrongly when replacing PRODUCT_DEFAULT_PROPERTY_OVERRIDES. Bug: 173452246 Test: build a Pixel device and check build.prop under system and vendor Change-Id: I86919f993ae44f3502eb63e728d33acaa14f7088 Merged-In: I86919f993ae44f3502eb63e728d33acaa14f7088
2020-11-25 09:58:52 +01:00
PRODUCT_VENDOR_PROPERTIES += ro.zygote?=zygote32
Add media_profiles_V1_0.dtd Test: media_profiles_V1_0.dtd exists in system/etc Bug: 36430270 Merged-In: I847a774baf2172d83d414f1794794089b383ded3 Change-Id: I847a774baf2172d83d414f1794794089b383ded3
2017-05-05 13:47:15 +02:00
Organize product vars for adding properties Properties for <partition>/build.prop are now added via PRODUCT_<PARTITION>_PROPERTIES. PRODUCT_SYSTEM_PROPERTIES is added. PRODUCT_SYSTEM_DEFAULT_PROPERTIES will be deprecated. PRODUCT_VENDOR_PROPERTIES is added. PRODUCT_PROPERTY_OVERRIDES and PRODUCT_DEFAULT_PROPERTY_OVERRIDES will be deprecated in favor of the new variable. For other partitions (odm, system_ext, product), there is no change. Exempt-From-Owner-Approval: cherry-pick from master Bug: 117892318 Test: m Merged-In: I98f3b5d0da661b3ad75260a23754e655103b7a44 (cherry picked from commit ad810b6dae32a42a828dfbddcaeec89f295d695e) Change-Id: I98f3b5d0da661b3ad75260a23754e655103b7a44
2020-05-29 10:50:03 +02:00
PRODUCT_SYSTEM_PROPERTIES += debug.atrace.tags.enableflags=0
PRODUCT_SYSTEM_PROPERTIES += persist.traced.enable=1
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
Indicate ANGLE is present on devices The system property ro.gfx.angle.supported needs to be enabled when ANGLE is included in a build to indicate to the platform and CTS tests that ANGLE is present on the device. Test: atest CtsAngleIntegrationHostTestCases Bug: 157670307 Merged-in: Ide4e3d8f78d3748d557a47ecd153d66694fd1e3a Change-Id: I72ba8731fed36dbc594dae88aaa00a6299e8f4ae
2020-08-11 02:42:22 +02:00
PRODUCT_PROPERTY_OVERRIDES += ro.gfx.angle.supported=true
Move perfprofd installation to PRODUCT_PACKAGES_DEBUG LOCAL_MODULE_TAGS is deprecated, use PRODUCT_PACKAGES_DEBUG instead. Test: none Change-Id: I670147f4fe38b02ccafe01b96d8078502404113c
2016-10-28 00:35:36 +02:00
# Packages included only for eng or userdebug builds, previously debug tagged
PRODUCT_PACKAGES_DEBUG := \
Remove embedded.mk The common mk files form a long chain of generic sounding names that don't make much sense. For instance, embedded, base, core_minimal, core and core_base all inherit each other, but there's no logical ordering of these names. The common mks will be split based on destination partition, which will create many new files. Merging some of the common ones before this split keeps the total number of mks under control. There are only 2 products inheriting this mk excluding base.mk (which has over 300 descendants). The other levels in the hierarchy all have multiple device categories rooted at them (e.g. wearables from base.mk, tvs and cars from core_minimal.mk), but embedded.mk has not which makes it a compelling target to remove. Bug: 80410283 Test: diff products variables with multiproduct_kati Change-Id: I35c05973dfefefb7a31686476215386b8b89a557
2018-06-18 13:21:17 +02:00
adb_keys \
Add previously debug tagged modules From external/iputils This had been accidentally skipped in automerger. Test: check installed files on userdebug builds Change-Id: I26e7cfa03f8a788283bce9c75fc38b4221cd57e6 (cherry picked from commit 0d78e197212cf092a4eb4a677a80f301f00fec8e)
2018-11-16 22:02:32 +01:00
arping \
Add dmuserd to PRODUCT_PACKAGES_DEBUG This is a simple dm-user daemon that will be used for the QA tests. Test: manual, b/171749628 Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com> Change-Id: I37b78a1479f08f37fe7cff3f2e201dc6d8a6e584
2020-10-31 00:44:58 +01:00
dmuserd \
Add previously debug-tagged modules These all had `LOCAL_MODULE_TAGS := debug` Test: treehugger Change-Id: I848d1d9fb7e9921827ef6b5b72376710150ce839
2019-01-18 23:47:41 +01:00
gdbserver \
Add CLI for Directly Invoking IDL APIs Test: Build and Flash Change-Id: I896423f884659b3081021abf243c63c8e17044df Signed-off-by: Harpreet \"Eli\" Sangha <eliptus@google.com>
2019-09-04 07:37:16 +02:00
idlcli \
Add previously debug-tagged modules These all had `LOCAL_MODULE_TAGS := debug` Test: treehugger Change-Id: I848d1d9fb7e9921827ef6b5b72376710150ce839
2019-01-18 23:47:41 +01:00
init-debug.rc \
Add iotop to PRODUCT_PACKAGES_DEBUG This was previously marked as LOCAL_MODULE_TAGS := debug, and is used from dumpstate. Test: iotop is still installed after remove the debug tag Change-Id: I685456f52403a2d5c6fbbff1429c6af422ce26df
2018-05-05 03:52:18 +02:00
iotop \
Add iperf3 to debug packages Bug: 123261826 Test: manual build Change-Id: Ia7639daccd8ec9e48dbc1e900669c821f73a8be7
2019-07-01 22:24:33 +02:00
iperf3 \
Add iw as a previously debug tagged module From external/iw Test: check installed files on debug builds Change-Id: Ie1282e88dfee47f958e13fd7ec17163f1178cb22
2018-11-16 22:14:42 +01:00
iw \
logcat: permit transition to Android.bp Permit transition of logcat to Android.bp by moving the debug target logpersist.start to the PRODUCT_PACKAGES_DEBUG list. Test: compile Change-Id: I6cfd4c40f848a2ff2661e3692fa8cd69ed99e8c9
2017-08-08 23:24:55 +02:00
logpersist.start \
Add previously debug-tagged modules These all had `LOCAL_MODULE_TAGS := debug` Test: treehugger Change-Id: I848d1d9fb7e9921827ef6b5b72376710150ce839
2019-01-18 23:47:41 +01:00
logtagd.rc \
Add showmap and procrank to PRODUCT_PACKAGES_DEBUG So that they are available on device by default. Test: make Change-Id: If3c1513d1c086f965a8adc157a96b35c119962c3
2018-06-27 23:14:06 +02:00
procrank \
Add profcollect to PLATFORM_PACKAGES_DEBUG ... but it does not get turned on automatically. This is controlled by profcollect_native_boot.enabled device config. Test: boot device and verify profcollectd is disabled by default Bug: 79161490 Change-Id: Ia91b9759e108896f275633e3156355b65dc94299
2020-11-04 02:44:27 +01:00
profcollectd \
profcollectctl \
Move remount to PRODUCT_PACKAGES_DEBUG. required seems to conflict with apex with the following error: build/make/core/main.mk:1338: warning: build/make/target/product/aosp_x86_64.mk produces files inside build/make/target/product/mainline_system.mks artifact path requirement. Test: treehugger Change-Id: Ifb1072b4585a94355909b33e3b8129455c35714a
2019-10-10 22:09:36 +02:00
remount \
Add showmap and procrank to PRODUCT_PACKAGES_DEBUG So that they are available on device by default. Test: make Change-Id: If3c1513d1c086f965a8adc157a96b35c119962c3
2018-06-27 23:14:06 +02:00
showmap \
Add strace back onto userdebug builds Blueprint stopped supporting the "debug" tag, per dwillemsen Change-Id: I6c206e058ce32cbea3fd8ae922ac1ba5a0598410
2017-10-17 20:50:16 +02:00
sqlite3 \
Add ss as a previously debug tagged module From external/iproute2 Test: check installed files on debug builds Change-Id: Ie2e1fc927f636602b1285f8b0e62a926d538b150
2018-11-16 22:35:51 +01:00
ss \
Build: Include lock-inversion agent in debug builds Bug: 124744938 Test: m Change-Id: Ieeaab84d2bc3db73dd8a6b19c05e4f39d90f22e0
2019-03-05 01:34:56 +01:00
start_with_lockagent \
Add sanitizer-status to PRODUCT_PACKAGES_DEBUG This ensures all -userdebug builds have the sanitizer-status binary, which is used to check which build flags were used for a given image. It is important to distinguish between what the build fingerprint claims, and what is actually available on the phone. Change-Id: Iac1eabb8c5ed885a057f7a302b1887b7e9c4ccbc
2018-04-03 22:19:44 +02:00
strace \
Add previously debug-tagged modules These all had `LOCAL_MODULE_TAGS := debug` Test: treehugger Change-Id: I848d1d9fb7e9921827ef6b5b72376710150ce839
2019-01-18 23:47:41 +01:00
su \
Add a few unwinder tools to debug tools. These tools are useful for dumping elf information. Also, some of the scripts in development are being modified to use some of these tools, specifically, unwind_symbols. Test: Do a clean userdebug build and verify that the tools are built. Change-Id: Id26b8d2220dc542e8aa73d4b701916fa3d2ea804
2018-07-20 20:22:03 +02:00
sanitizer-status \
Add previously debug tagged modules From external/iputils This had been accidentally skipped in automerger. Test: check installed files on userdebug builds Change-Id: I26e7cfa03f8a788283bce9c75fc38b4221cd57e6 (cherry picked from commit 0d78e197212cf092a4eb4a677a80f301f00fec8e)
2018-11-16 22:02:32 +01:00
tracepath \
tracepath6 \
traceroute6 \
Add a few unwinder tools to debug tools. These tools are useful for dumping elf information. Also, some of the scripts in development are being modified to use some of these tools, specifically, unwind_symbols. Test: Do a clean userdebug build and verify that the tools are built. Change-Id: Id26b8d2220dc542e8aa73d4b701916fa3d2ea804
2018-07-20 20:22:03 +02:00
unwind_info \
unwind_reg_info \
unwind_symbols \
Move the old user tagged modules over to base.mk so mini and core both share them. Change-Id: I9d3a3c165fa56d4ca137b3c06e249e1deea6a1c5
2012-07-24 03:20:07 +02:00
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
# The set of packages whose code can be loaded by the system server.
PRODUCT_SYSTEM_SERVER_APPS += \
SettingsProvider \
WallpaperBackup
Add PRODUCT_PACKAGES_DEBUG_ASAN This is a list of modules which should be installed by default, but only on builds which are set up for Address Sanitizer (via SANITIZE_TARGET=address). Additionally, add sanitizer-status to PRODUCT_PACKAGES_DEBUG so that all userdebug builds will have the binary. Currently, the module has the "debug" tag but it may go away in the future. Change-Id: I0bea4faf9c2a65380292471437e51ef8324b5af3
2018-03-26 23:17:03 +02:00
# Packages included only for eng/userdebug builds, when building with SANITIZE_TARGET=address
Add 'honggfuzz' and 'fuzz' to all ASAN / coverage builds 'hongfuzz' is a the interface to all honggfuzz fuzzers. Unlike libFuzzer, where the entry point *is* the fuzzer binary, honggfuzz uses a separate binary to drive fuzzing. 'fuzz' is a wrapper script that performs some device-side setup and sanity checks for fuzzing sessions, while providing a simple interface to all user-space fuzzers. Change-Id: Ia55d517e9cb1b7bfcd7d29b137b691e74398ca9e
2018-04-03 22:25:09 +02:00
PRODUCT_PACKAGES_DEBUG_ASAN := \
fuzz \
honggfuzz
Add PRODUCT_PACKAGES_DEBUG_ASAN This is a list of modules which should be installed by default, but only on builds which are set up for Address Sanitizer (via SANITIZE_TARGET=address). Additionally, add sanitizer-status to PRODUCT_PACKAGES_DEBUG so that all userdebug builds will have the binary. Currently, the module has the "debug" tag but it may go away in the future. Change-Id: I0bea4faf9c2a65380292471437e51ef8324b5af3
2018-03-26 23:17:03 +02:00
Modify build to put dumpcoverage agent into /system/lib This location allows the agent to be attached to arbitrary processes. It only makes sense to include libdumpcoverage.so on coverage builds, as these are the only builds that have any information to be dumped. Test: manual, used examples in README (see other CL) to test whether it works on a userdebug_coverage build on cuttlefish Change-Id: Ib2fece1b41a3b5d16c8a2a444c5486137e475fda
2019-06-11 19:27:47 +02:00
PRODUCT_PACKAGES_DEBUG_JAVA_COVERAGE := \
libdumpcoverage
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
PRODUCT_COPY_FILES += $(call add-to-product-copy-files-if-exists,\
Update paths for frameworks/base/config Bug: 64259751 Test: make Change-Id: Ie159ef9f3f96d7ecd22429327a64161bd63f525b
2017-08-11 23:43:53 +02:00
frameworks/base/config/preloaded-classes:system/etc/preloaded-classes)
Install preloaded-classes as a standalone configuration file Install preloaded-classes as a standalone configuration file /system/etc/preloaded-classes, so we can configure different file per product. To override the default frameworks/base/preloaded-classes, just override in your product configuration makefile with PRODUCT_COPY_FILES before it inherits from build/target/product/base.mk: if there are multiple items in PRODUCT_COPY_FILES with the same destination, the first one takes precedence. Bug: 18305157 Change-Id: I937632b4a1aa73310ec90e73fd708fbd0c704a21
2014-11-14 00:19:12 +01:00
Add dirty-images-objects handling to boot image build. Allows grouping of classes with dirty static fields to be grouped together in the image to have fewer dirty pages. Bug: 62554875 Test: mm test-art-host Change-Id: I2486d2704d74a192f1ecdc02589e569b61efa4ae
2017-08-03 01:45:49 +02:00
# Note: it is acceptable to not have a dirty-image-objects file. In that case, the special bin
# for known dirty objects in the image will be empty.
PRODUCT_COPY_FILES += $(call add-to-product-copy-files-if-exists,\
Update paths for frameworks/base/config Bug: 64259751 Test: make Change-Id: Ie159ef9f3f96d7ecd22429327a64161bd63f525b
2017-08-11 23:43:53 +02:00
frameworks/base/config/dirty-image-objects:system/etc/dirty-image-objects)
Install preloaded-classes as a standalone configuration file Install preloaded-classes as a standalone configuration file /system/etc/preloaded-classes, so we can configure different file per product. To override the default frameworks/base/preloaded-classes, just override in your product configuration makefile with PRODUCT_COPY_FILES before it inherits from build/target/product/base.mk: if there are multiple items in PRODUCT_COPY_FILES with the same destination, the first one takes precedence. Bug: 18305157 Change-Id: I937632b4a1aa73310ec90e73fd708fbd0c704a21
2014-11-14 00:19:12 +01:00
Keystore 2.0: Disable keystore 2 by default (for now) Test: System starts without keystore 2 running. Bug: 160623310 Change-Id: I83d54de602a0f70acc91fd8e55b07706e1b4e55b
2021-02-05 21:17:10 +01:00
# This property allows enabling Keystore 2.0 selectively for testing.
# TODO Remove when Keystore 2.0 migration is complete. b/171563717
PRODUCT_SYSTEM_PROPERTIES += persist.android.security.keystore2.enable=false
Dedupe mk rules in core_minimal.mk and core_tiny.mk. These two are the only ones inheriting base.mk, and were largely similar. This CL moves all the shared stuff up one level into base.mk. One thing not de-duped yet is the PRODUCT_SYSTEM_SERVER_JARS variable, as the order of that is significant. Also sort various lists that were ordered arbitrarily. Bug: 80410283 Test: diffed output of multiproduct_kati with aosp/703385 patched Change-Id: Iddffd6982df039f5daa8be345de338ba11c63c10
2018-06-08 15:42:06 +02:00
$(call inherit-product, $(SRC_TARGET_DIR)/product/runtime_libart.mk)
Reference in a new issue Copy permalink