This is used to force HIDL to be enabled for device bring-up when
partners have converted all of their AOSP HAL implementations to AIDL,
but still have some partner-owned interfaces that they are working on
converting from HIDL TO AIDL.
Test: PRODUCT_HIDL_ENABLED = true && adb shell lshal
Test: PRODUCT_HIDL_ENABLED = false && adb shell lshal
Bug: 332548148
Change-Id: I6e6dc6c9e22d31c270e3c3520fc074bbeb349808
Removal of this additional special-casing was missed in aosp/3028110
Test: presbumits
Test: used go/abtd to test a handful of targets in tv's release branch
Bug: 308188056
Change-Id: I6af3821f53e0ceeb0c48c921a0c851b9e6d2d5b6
`is_unit_test` is removed from module-info.json by mistake.
Bug: 309006256
Test: m out/target/product/vsoc_x86_64/module-info.json
Change-Id: I03ccc0efec83fbf5a0c6e548941bba6467ce8cd1
All tv devices on internal CI branches currently build in trunk_staging
config. Since trunk_staging provides sources of mainline modules via
RELEASE_APEX_CONTRIBUTIONS_*, we do not need this special-casing
anymore.
(cs query
https://source.corp.google.com/search?q=ATV.*TARGET_RELEASE.*next%20f:%5C.gcl&sq=)
Test: presbumits
Test: used go/abtd to test a handful of targets in tv's release branch
Bug: 308188056
Change-Id: Iaadd5b9151c8cce3fe0a193f2e5c37d63e6095d4
rust_ffi_static right now will export excessive symbols, this lead to a
duplication of symbols when aconfig links against both
libaconfig_storage_file_cc and libaconfig_storage_read_api_cc. This is
because aconfig_storage_read_api crate depends on aconfig_storage_file
crate. To solve this problem, move create flag info file api to
aconfig_storage_write_api crate which is parallel to
aconfig_storage_read_api crate.
Bug: b/321077378
Test: atest aconfig_storage_file.test; atest
aconfig_storage_read_api.test; atest aconfig_storage_write_api.test
Change-Id: Ibbb50193a2da82d52ccbb4087c8e3fb9f320805f
exported mode
The exported mode library will be dropped into google3, and there isn't
the library for this annotation.
Test: atest aconfig.test
Bug: n/a
Change-Id: I318d1c0faf232b22f42587b8ea2f976173c8554a
Enabling TARGET_NO_BIONIC_PAGE_SIZE_MACRO implies those targets no
longer rely on the `PAGE_SIZE` bionic macro. Page size would be queried
at runtime using getpagesize() / sysconf(_SC_PAGE_SIZE).
This re-applies commit 9014163717 and also
updates the VSR_VENDOR_API_LEVEL for which
TARGET_NO_BIONIC_PAGE_SIZE_MACRO is set to false from < 34 to < 35 (As
this needs to be enabled only for Android V targets).
Test: lunch <target> && get_build_var TARGET_NO_BIONIC_PAGE_SIZE_MACRO
Bug: 310232825
Change-Id: I4a79939b129dd7ae6a50e8aa4719a9d8413156fb
Add new folks working on finalization, remove folks no longer working on
it.
Also, sort the entires alphabetically.
Bug: 323940469
Test: N/A
Change-Id: Ib8f6c3f485a06e3d1269e4142317174ae7ac276b
(This relands aosp/3007754 with additional handling for go apexes. The
additional handling was added in internal in ag/26705862, so we need to
add this to aosp as well)
The ignore list is burdensome to maintain once we start adding the
module sdk contents to apex_contributions. Convert the variable to a
boolean. When set to true, all contents in `apex_contributions` will be
ignored
Test: m nothing on aosp,google and google_fullmte devices
Ignore-AOSP-first: CL topic does a cleanup of an internal only denylist
Merged-In: If899f6eaf5449c2aa789d0bd5b791a3db715c676
Merged-In: I4532f3743eb3b7121e1f5e522097c1aba3d9a4fd
Change-Id: I18db6657b78b2741c7f9af9e9d0150f85edeeda7
This is already added in product/media_system_ext.mk so it doesn't need
to be added again.
Test: m
Bug: 332548148
Change-Id: I11be0c8f2fb788df19df7e531ed3d8e3b1381d0f
`sdk` builds require sources of mainline modules. explicitly set this
value to prevent reaching an incompatible state across release build
flags and soong config namespaces prebuilt vs source selection
mechanism.
Test: will use go/abtd to run the failing target in b/332322437
https://android-build.corp.google.com/builds/abtd/run/L54400030002940286
Bug: 332322437
Change-Id: If65fb3706910ac5142d6ad9dc416190fa1c9ee89
Previously, three seperate crates create their own test baseline which
are nearly identical. This is inconvinent when updating the baselines.
All three locations needs to be touched. This cl merges functions to
create test storage file base struct into aconfig_storage_file crate
Bug: b/321077378
Test: atest aconfig.test
Change-Id: Ic97437f856763347a11de8b449592292014bcce3
Move the executes `berberis_host_tests_result` and
`berberis_run_host_tests` to `build/core/tasks`, as Soong might
currently have difficulty supporting this part.
Set the OWNER of berberis_test.mk
Bug: 321643544
Test: 1. lunch sdk_phone64_x86_64_riscv64-trunk_staging-eng
2. m berberis_all
3. m berberis_host_tests_result
4. m berberis_run_host_tests
Change-Id: I44a03e9eae9ee6a3c82a6d2e6de3a03b2c7d81da
VSR_VENDOR_API_LEVEL is used to know the vendor API level for the VSR
requirement.
This must have the same value with the ro.vendor.api_level on run
time.
Bug: 332401254
Test: get_build_var VSR_VENDOR_API_LEVEL
Change-Id: I8e1fac8f05e4b06128738f377d63f26567d3902b
Check that device is shipped supporting v3 in order to enable it.
Otherwise fallback.
Bug: 331202590
Test: th
Change-Id: I218fbaa6a044420af39be70b055da5ffbfced158
