expose the flag to soong. the flag is to indicate a custom VM can
use para-virtualized devices.
Bug: 333495394
Test: build
Change-Id: I4e1854b5701302ae0ec1bf73862f264642b6e418
As of VNDK deprecation, BOARD_VNDK_VERSION should not be referenced
anymore. This change removes BOARD_VNDK_VERSION references and related
logics from Kati, so VNDK deprecation can be fully set without flag.
Bug: 330100430
Test: AOSP CF build succeeded
Change-Id: I9ea5f1236268b99eb731ebf48afd9e595d06ab1a
soong config vars are no longer needed to support the following two
special cases
1. Santized builds. google hwasan products have been updated to explicitly list
PRODUCT_MODULE_BUILD_FROM_SOURCE ag/26576335
2. Coverage builds. product specific overrides of build flags are not
possible, so apex_contributions.go has been special cased to ignore
prebuilts. Since RELEASE_APEX_CONTRIBUTIONS_* are now used to select
prebuilts of mainline modules, we can drop the special-case of
coverage builds in this .mk file
Bug: 308188056
Bug: 325666427
Test: lunch cf_x86_64_phone-next-userdebug && EMMA_INSTRUMENT=true m
nothing; # verified that no path exists between droid and the prebuilt
bt apex
Change-Id: Ide50e4463615fef5f540130f6a6bce50c00eddb8
This reverts commit 1ecbeae2dd.
Reason for revert: Prime candidate as culprit for build breakage
build_id/11678886
Bug: 333111739
Change-Id: I24ee63b7cfe738e505e691b2d111c4a816513657
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
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
