We must use `deps`, not `multilib.lib64`, because uprobestats is a
native binary and we also consider 32-bit targets.
Bug: 381019944
Test: build all aosp_{target} targets
Change-Id: I001ac687ffc3874719ad9f685690b36729192aa0
This reverts commit c125acc4c502ef19479bdb8dda3b8ddc520199b1.
Reason for revert: build breakage fixed with aosp/3486213
Change-Id: Iad7ee9ab188b2b387ec07d34cd6245aeb568ae4f
This reverts commit a927af6775.
The original change breaks building vendor image for legacy A/B devices
with a recovery partition. Because build checks the out image size plus
the recovery patch size. If sparse images are disabled, then the output
image size will always be the max size. And max size plus anything will
always be greater than max size.
Change-Id: I87dd2bf78e9080d1fc2d320df7e98ee98efa031c
(cherry picked from commit 008ed588707f277e0e63f0b70d5fd6b598220e51)
This change corrects a typographical error in the Soong configuration
for chre_daemon_lpma_enabled.
Bug: 374901347
Test: m -j chre
Change-Id: Iab7e7da50d4b66475faf75b0510b62a6a77e9584
This reverts commit 239c5308eb.
Reason for revert: This breaks targets that use _only_
DEVICE_MANIFEST_SKUS and DEVICE_MANIFEST_<SKU>_FILES,
since vendor_manifest.xml is non existent on those targets.
The original change assumed it would be possible to add an entry
to PRODUCT_PACKAGES even if not existing, but that's not the case.
In the soong-only case this may work as we'd simply skip the
module installation via m.SkipInstall(), but when generating
Android.mk, as vintf_data does, that's not possible.
Test: m on qualcomm device which only contains SKU specific manifests
Change-Id: I3e4e8f9087640608643cc726bcfa0658467745eb
-----BEGIN PGP SIGNATURE-----
iF0EABECAB0WIQRDQNE1cO+UXoOBCWTorT+BmrEOeAUCZ8epCAAKCRDorT+BmrEO
eG6dAJwJy3IdODd+HgUsdj7MVmwkqygGqwCeJviycaHuBg1VVbQQcM3fOEZMM4c=
=0HrU
-----END PGP SIGNATURE-----
gpgsig -----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgPpdpjxPACTIhnlvYz0GM4BR7FJ
+rYv3jMbfxNKD3JvcAAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
AAAAQAM+iWabmFo75HYa/mtMLW3NlCIZQih468Ad8KckTSDMjrD7edVX4c5quzeDnOdzvI
l267FNZnLg68A5vPP1iQo=
-----END SSH SIGNATURE-----
Merge tag 'android-15.0.0_r20' into staging/lineage-22.2_merge-android-15.0.0_r20
Android 15.0.0 Release 20 (BP1A.250305.019)
# -----BEGIN PGP SIGNATURE-----
#
# iF0EABECAB0WIQRDQNE1cO+UXoOBCWTorT+BmrEOeAUCZ8epCAAKCRDorT+BmrEO
# eG6dAJwJy3IdODd+HgUsdj7MVmwkqygGqwCeJviycaHuBg1VVbQQcM3fOEZMM4c=
# =0HrU
# -----END PGP SIGNATURE-----
# gpg: Signature made Wed Mar 5 03:29:44 2025 EET
# gpg: using DSA key 4340D13570EF945E83810964E8AD3F819AB10E78
# gpg: Good signature from "The Android Open Source Project <initial-contribution@android.com>" [ultimate]
* tag 'android-15.0.0_r20': (513 commits)
Version bump to BP1A.250305.019 [core/build_id.mk]
Version bump to BP1A.250305.018 [core/build_id.mk]
Version bump to BP1A.250305.017 [core/build_id.mk]
Version bump to BP1A.250305.016 [core/build_id.mk]
Version bump to BP1A.250305.015 [core/build_id.mk]
Version bump to BP1A.250305.014 [core/build_id.mk]
Version bump to BP1A.250305.013 [core/build_id.mk]
Version bump to BP1A.250305.012 [core/build_id.mk]
Version bump to BP1A.250305.011 [core/build_id.mk]
Version bump to BP1A.250305.010 [core/build_id.mk]
Version bump to BP1A.250305.009 [core/build_id.mk]
Version bump to BP1A.250305.008 [core/build_id.mk]
Version bump to BP1A.250305.007 [core/build_id.mk]
Version bump to BP1A.250305.006 [core/build_id.mk]
Version bump to BP1A.250305.005 [core/build_id.mk]
Update update_bootloader_radio_image.mk calling path
Version bump to BP1A.250305.003 [core/build_id.mk]
Version bump to BP1A.250305.002 [core/build_id.mk]
Version bump to BP1A.250305.001 [core/build_id.mk]
Version bump to BP1A.241210.028.A1 [core/build_id.mk]
...
Conflicts:
core/Makefile
core/android_soong_config_vars.mk
core/build_id.mk
core/config.mk
core/sysprop.mk
target/product/security/Android.mk
Change-Id: I9b26bf1f864b9b864a27d2bac2fc382a2da42803
Some kind of extras needs to alter variables that becomes read-only
after inclusion of board_config.mk, or wants some variables getting
processed by board_config.mk. For example, native bridge.
Change-Id: If7ef0dcfc30b52940017662fa7402e4970dbc3c7
Android 15.0.0 Release 14 (AP4A.250205.002)
# -----BEGIN PGP SIGNATURE-----
#
# iF0EABECAB0WIQRDQNE1cO+UXoOBCWTorT+BmrEOeAUCZ6KKlwAKCRDorT+BmrEO
# eHPMAJ46I/qLkqi7OVomW/h6t3WIjZnWWgCbBWRJZelNypk3B7l1z/ixuLNFtV4=
# =u7Fz
# -----END PGP SIGNATURE-----
# gpg: Signature made Tue Feb 4 23:45:59 2025 EET
# gpg: using DSA key 4340D13570EF945E83810964E8AD3F819AB10E78
# gpg: Good signature from "The Android Open Source Project <initial-contribution@android.com>" [ultimate]
# By Android Build Coastguard Worker
# Via Android Build Coastguard Worker
* tag 'android-15.0.0_r14':
Version bump to AP4A.250205.002 [core/build_id.mk]
Version bump to AP4A.250205.001 [core/build_id.mk]
Version bump to AP4A.250105.002.C1 [core/build_id.mk]
Version bump to AP4A.241205.004.R1 [core/build_id.mk]
Version bump to AP4A.250105.002.B1 [core/build_id.mk]
Version bump to AP4A.250105.002.A1 [core/build_id.mk]
Change-Id: I5f363a7abb853aae26aeb25c400e377eb0a6a8a8
llvm-readobj is valid for other object file types such as PE/COFF, so
some firmware files are wrongly detected as ELF prebuilts. Additionally
check the output of llvm-readobj to avoid such false positives.
Change-Id: I4c4ede747967b4a1213aadaed2f925672d18579c
