Bug: 135956699
Test: m -j30 (verify that build includes CellBroadcastServiceModule)
Change-Id: Ib2d734ba2ed3608a4255164e6e50dac349eb9a18
Merged-In: Ib2d734ba2ed3608a4255164e6e50dac349eb9a18
The default packages for system_ext partition must be added to
*_system_ext.mk.
We have empty list for now, but will update the files soon.
Bug: 134359158
Bug: 139053989
Test: build and boot
Change-Id: I78c85c3a9ff0437906143c2d4982ecfb0e4d058d
In Factory OTA, secondary payload should be generated without
virtual_ab flag set, so that update package generator generates
a regular A/B OTA (with snapshot_enabled set to false), and
OTA client writes system_b without snapshots.
Test: apply secondary OTA
Fixes: 138733621
Change-Id: I05d534a12d4a7891ce5597f3c29e55f5185e5a8d
am: efdd1abdf6 -s ours
am skip reason: change_id Iee2ac89586d71d9ab3bb257f2b3b1073710554d5 with SHA1 670e6d74aa is in history
Change-Id: I7d2431e25b7703e5e4c4f16fbebd3898544ef795
am: 27fe9add1d -s ours
am skip reason: change_id Iee2ac89586d71d9ab3bb257f2b3b1073710554d5 with SHA1 670e6d74aa is in history
Change-Id: I8df1e5dd0f1033b46aea07552f8f42a08eb0e7ca
am: d24005d853 -s ours
am skip reason: change_id Iee2ac89586d71d9ab3bb257f2b3b1073710554d5 with SHA1 8c1290cbd5 is in history
Change-Id: I3e3edd83819534828039175782ea3a2c8b6bee2b
Path conflicts could happen when following conditions are met.
1) a java library named "foo" is not installable.
2) a java library named "bar" is installable, and its stem is set to
"foo".
Then the notice file for 1) becomes foo.jar.txt following its
LOCAL_MODULE, while the notice file for 2) becomes foo.jar.txt following
its stem. Since the file for 1) is a synthetic one, the actual name
isn't important. Avoid the conflict by appending a suffix
(_non_installable, but could be anything) to the file name for 1).
There still is a chance for the conflict; if the stem for "bar" is set
to "foo_non_installable". But practically, the chances are very low.
Bug: 139391334
Bug: 143700028
Test: m
Change-Id: Id50b30774bbf65cc180baf963a95ea56fe6eb74f
Use the same procedure to avoid code duplication.
Note that dump-dynamic-partitions-info not only has more information,
but also changes keys:
- from X_size to super_X_group_size
- from X_partition_list to super_X_partition_list
delta_generator is updated to recognize these new keys as well.
Test: build ota package
Test: forrest
Change-Id: I6a973fc113fb80b352822a14991cad027c72cf06
AOSP targets doesn't have INSTALLED_VENDORIMAGE_TARGET defined.
Fix dump-dynamic-partitions-info to filter out vendor
from dynamic partition lists.
Then, check_partition_sizes.py reads info without vendor
in dynamic partition list for AOSP targets.
Test: forrest
Bug: 143734706
Change-Id: I788196d854c1cf3eea218d534599f8bf642120fc
We are bringing up support for ARM Memory Tagging Extension in the platform,
but the required patches have not yet landed in the upstream kernel. This
change adds support for a product variable that products may set to true to
declare support for an experimental userspace interface to MTE. Setting the
variable to true causes a product configuration to be enabled which will
activate code in bionic and scudo that uses the interface.
This variable should not be set to true in shipping products because
the userspace interface has not been finalized and is subject to change.
Once the support patches have landed in the kernel, bionic and scudo will
be changed to use the official interface and the variable will be removed.
Bug: 135772972
Change-Id: Ie3d2619bc09c134e0da073c65805e7ec049687e1
We were passing "--classpath foo.jar --classpath bar.jar" to turbine,
it now wants (and may always have expected?)
"--classpath foo.jar bar.jar".
This is equivalent to Ib7e0ca64a34e236110f7b785d6a0fb51ed75567e in
Soong.
Test: m java
Change-Id: I061ebf302a215c66b1923056716b60bf0160d9bc
turbine supports taking system modules on the command line,
now that we target Java language level 1.9 and use system modules
by default switch turbine to match javac.
This is equivalent to Ieee07502151da0d5693bb8929213d495c039106b
in Soong.
Test: m java
Change-Id: Ib91c6f57b316f48f1ab819e4e1d2dc2e0ee42988
Dexpreopt build commands should only be generated on targets that
include build/make/target/product/runtime_libart.mk, which sets the
necessary variables such as PRODUCT_SYSTEM_DEFAULT_PROPERTIES that
contain default values passed to dex2oat. This file also sets a
variable PRODUCT_USES_DEFAULT_ART_CONFIG that is used in
build/make/core/dex_preopt.mk to decide if boot images should be
installed.
On some targets build/make/target/product/runtime_libart.mk is not
included. Prior to this patch, on such targets invalid dexpreopt
commands were generated, but not used, so they did not cause any
visible build failures. The invalid commands can be grepped as:
lunch qemu_trusty_arm64-userdebug && m nothing \
&& fgrep -e '-Xms ' $ANDROID_BUILD_TOP/out/soong/build.ninja
In this case '-Xms ' is an ill-formed option passed to dex2oat (the
option expects one argument, but none is passed).
This patch makes the DisablePreopt variable passed from make to
soong more strict: it not only requires WITH_DEXPREOPT, but also
PRODUCT_USES_DEFAULT_ART_CONFIG. This means that dexpreopt commands
will not be generated on targets that do not include
build/make/target/product/runtime_libart.mk.
Test: lunch aosp_walleye-userdebug && m \
&& find $ANDROID_BUILD_TOP/out -name 'boot.art'
# expect to find files in /out/target/product/walleye/system/framework/$ARCH/
Test: lunch qemu_trusty_arm64-userdebug && m \
&& fgrep -e '-Xms ' $ANDROID_BUILD_TOP/out/soong/build.ninja
# expect empty output
Change-Id: I3d765ed0dd8b38236b8bdd5c6202bb1d3f45f904
am: 3fa302e04f -s ours
am skip reason: change_id I2a32694b899bc4f0a0ba36b152c06689427dabf4 with SHA1 820f20e990 is in history
Change-Id: I5a5d4dae1e64a80c8482193ce723c7d9d2d4b695
Jordan Liu