This is a follow-up CL for https://r.android.com/1900565.
This is needed because product makefiles may need to add their own
APEX boot jars, and they cannot insert them in the correct alphabetical
order on the list. So it needs to be sorted automatically. Do this
after processing all product makefiles and populating the variable,
but before passing it to Soong.
Bug: 207474880
Test: lunch aosp_cf_x86_64_phone-userdebug && launch_cvd
# cuttlefish device boots successfully
Change-Id: I86b58ef8aeac595e401d872f59a2936a67bedeec
dexopt defaults to dex2oat32 unless instructed otherwise. Since
dex2oat32 doesn't exist on a 64-bit-only build, make sure dex2oat64
is selected instead.
Test: boot aosp_cf_x86_64_only_phone and check that installd doesn't
try to use dex2oat32
Change-Id: Ia67e746894684a52a4e5b765bfde0f6dd0efbf6e
Used ~/master/development/tools/make_key with the subject '/C=US/ST=California/L=Mountain View/
O=Android/OU=Android/CN=Android/emailAddress=android@android.com' to create the certificate and key
Bug: 203670791
Test: make, Device boots
Change-Id: Ib0cdf7786c7f74cf294c54187649114e8ec6d315
This is needed because product makefiles may need to add their own
system server jars to this variable, and they cannot insert them in
the correct alphabetical order on the list. So it needs to be sorted
automatically. Do this after processing all product makefiles and
populating the variable, but before passing it to Soong.
Bug: 207474880
Test: atest art_standalone_dexpreopt_tests:art_standalone_dexpreopt_tests.DexpreoptTest#ForSystemServer
Change-Id: I80dbf555c395c92539c506d3d8b1f2f101a58bce
builds (reland).
- Use art/build/boot/boot-image-profile.txt for the primary boot image
in the ART module, both when it's built from source in platform and
as an unbundled module.
- Use frameworks/base/boot/boot-image-profile.txt for the framework
extension image in platform, but not in unbundled builds.
This should obsolete the combined profile
frameworks/base/config/boot-image-profile.txt.
This relands https://r.android.com/1881863 with a fix to allow multiple
values on PRODUCT_DEX_PREOPT_BOOT_IMAGE_PROFILE_LOCATION.
Test: build/soong/soong_ui.bash --dumpvar-mode \
PRODUCT_DEX_PREOPT_BOOT_IMAGE_PROFILE_LOCATION
and check that it prints both art/build/boot/boot-image-profile.txt
and frameworks/base/boot/boot-image-profile.txt in a platform build
on master.
Test: build/soong/soong_ui.bash --dumpvar-mode \
PRODUCT_DEX_PREOPT_BOOT_IMAGE_PROFILE_LOCATION
and check that it prints only art/build/boot/boot-image-profile.txt
in an unbundled build on master-art.
Test: banchan com.android.art && m
on master-art and check that
out/soong/.intermediates/art/build/apex/com.android.art/android_common_com.android.art_image/image.apex/javalib/x86_64/boot.oat
shrinks from 14 MB to 4.7.
Test: m droid
on master together with https://r.android.com/1895131 and check that
out/soong/.intermediates/art/build/apex/com.android.art/android_common_com.android.art_image/image.apex/javalib/x86_64/boot.oat
and out/target/product/vsoc_x86_64/system/framework/x86_64/boot-framework.oat
are identical.
Test: lunch armv8-eng && art/tools/buildbot-build.sh
on master-art
Bug: 174746397
Change-Id: I9114271bc69cf0888150b2c778a086bc50b73045
This reverts commit 1f925ed13e.
Reason for revert: SH regressions in boot and app startup: b/206152027
Bug: 174746397
Bug: 206152027
Change-Id: I60f642b8e4dd8ea04248b835e5b76ffcf01ac300
Please let me know if there's some other config
where this might be a better fit instead.
The earlier prototyping work that established the
first "delegate chooser" component (i.e.
"Phase 2" of go/sharesheet-unbundling-phases)
implemented that component in SystemUI, which is
explicitly referenced only in handheld_system_ext.
OTOH the original ("system") Sharesheet comes
from frameworks/base, so for parity it seems like
this probably belongs in base_system instead.
Note that this still has no user-observable
effect; the IntentResolver component is only
invoked under the DeviceConfig flag
`systemui::use_delegate_chooser` which is
currently false for all users who haven't
manually opted-in.
Bug: 202164690
Test: Manually tested functionality on raven
after `mp droid` (or more easily, just confirm
the presence of the component by
`adb shell pm list packages` and check for
`package:com.android.intentresolver`).
Change-Id: I04579cd722fe5c04b4ce3fc1cc291b272c7ebab2
