am skip reason: Merged-In I0cabba5faa4535dcdff3aa8b87aa61ac06ac9edb with SHA-1 ea0c5565db is already in history
Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/26395025
Change-Id: I2ab5c8c57727d093de1b976753b78002906eda7b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Currently the default flag values are not loaded into sysprop. Since the
current requirements for export flag are for flagged api in java and the
new storage system will load default values for all, there won't be
changes to make the default value loaded into sysprop. Thus this change
disable export mode for generated native flag libraries for now. It will
be enabled once the new storage is landed.
Test: m libaconfig_test_rust_library_with_exported_mode and expect build
failure
Bug: 327392334
Change-Id: I2db814d015cdb533778822f7417d055b251ed589
This bump includes Adservices, HealthFitness, Mediaprovider, Tethering, Extservices
Bug: b/327320298
Test: The build passes
Ignore-AOSP-first: Finalization is not performed in AOSP
Change-Id: I519a7238800aa49a595aac88f6c738c154f7a503
Merged-In: I0cabba5faa4535dcdff3aa8b87aa61ac06ac9edb
If a device's source or target cow version is specified at 2 (or
undefined) we should fallback on using the v2 writer.
e.g.
1. v3 -> v2 downgrade OTA
2. v2 -> v3
Bug: 322279333
Test: ota_from_target_files
Change-Id: I8c5139eceeb64ee255ddea66017b3e17bbdc44c0
Different prebuilts might have different contents and thus, different
boot jars to be removed from the existing apex boot jar lists e.g. next
using U prebuilts would need to remove framework-pdf while ap31 with V
prebuilts must not remove such. The existing mechanism will always
remove framework-pdf whenever prebuilts are enabled regardless of
release config, which is not correct in context of multiple prebuilt
support.
Ignore-AOSP-First: for successful build, we need to submit this togther with ag/26332775. this cl will get cp'ed into aosp later on
Bug: 327022391
Test: build device in next and trunk
Merged-In: I9949fb7075ab6c207a292f13fd75e010a4958f87
Change-Id: I9949fb7075ab6c207a292f13fd75e010a4958f87
The 1p files are included in PRODUCT_COPY_FILES and released with products.
Bug: 316805918
Test: CIs
Change-Id: Ibe443af26fb14c1bd84552c9f327a1c2ba8c70a4
Different prebuilts might have different contents and thus, different
boot jars to be removed from the existing apex boot jar lists e.g. next
using U prebuilts would need to remove framework-pdf while ap31 with V
prebuilts must not remove such. The existing mechanism will always
remove framework-pdf whenever prebuilts are enabled regardless of
release config, which is not correct in context of multiple prebuilt
support.
Ignore-AOSP-First: for successful build, we need to submit this togther with ag/26332775. this cl will get cp'ed into aosp later on
Bug: 327022391
Test: build device in next and trunk
Change-Id: I9949fb7075ab6c207a292f13fd75e010a4958f87
Some devices would like to use sources of mainline modules
even in next builds. This CL uses PRODUCT_MODULE_BUILD_FROM_SOURCE to
ignore the apex_contributions specified in the shared google_device's next.scl
Long term, this will be implemented by creating a product specific
release config map for this family of devices
Test: lunch <device>_fullmte-next-userdebug && m nothing
Bug: 325666427
Ignore-AOSP-First: The CL touches an internal only allowlist
Change-Id: I0cabba5faa4535dcdff3aa8b87aa61ac06ac9edb
This CL removes the SYSTEMUI_USE_COMPOSE build flag, which is now
enabled by default on all SystemUI variants.
Bug: 295304993
Test: mp droid
Ignore-AOSP-First: Flag was introduced in internal tree in
ag/20785186
Change-Id: I2f2b6b66262eefe2f0b0821773fda4cc07526d7b
Devices may set its first vendor api level to
PRODUCT_SHIPPING_VENDOR_API_LEVEL. This will manually set to
ro.vendor.api_level and will be used by tests.
If this value is not defined, init process will automatically
calculate the ro.vendor.api_level property for tests.
Bug: 326164316
Test: Check vendor/build.prop
Change-Id: I89f844ffaad9e3e39deab1c680bd1f7f17f4d8ad
Introduces ide_query_cc_analyzer, which figures out relevant build targets that needs to be built for a given C++ source or header file.
Once these targets are built, it analyzes the sources in question and reports any generated files that are used back.
Full ide_query integration relies on this binary also being available in prebuilts clang-tools, it'll be done in a future patch.
Change-Id: Ib0ef6da7a2bc8ecf66940b326e037fb1ee230bf9
This change puts base_system and default_art_config references to
the profiling module behind the build flag.
It also adds the flag to soong_config_vars so it can be referenced
from the Profiling module and from platform_bootclasspath.
Bug: 293957254
Bug: 325523640
Test: Built locally on trunk_food (where flag is disabled) and
trunk_staging (where flag is enabled.)
Ignore-AOSP-First: Must be submitted in topic with internal-only
changes.
Change-Id: I51cfa65ff607753cc8c588793ea381419ac99260
Update the state to 'vintf' so we don't try to re-finalize the same
level.
Ignore-AOSP-First: VINTF 202404 Finalization
Bug: 279809333
Test: build
Change-Id: I06530eedaeb69cc9d4a9b3af5b91a101ab2eab7d
