supporting negative compression levels in ota_from_target_files in the
format of zstd,-$compression_level
Test: ota_from_target_files
Change-Id: If2ca592829f10e7a0226cb41680cb47223d17c71
Now we are storing flag index instead of flag byte offset in storage
files, need to update storage write api accordingly.
Bug: b/321077378
Test: atest -c
Change-Id: I67e55287a242df0af1925ede886f8c087d343c1f
With the update to store flag index instead of flag byte offset in
storage file. We need to update flag read api accordingly.
Bug: b/321077378
Test: atest -c
Change-Id: Iccbf939fc5b7fe0ce0f2c33f7e3aa403c268120a
Previously, in package.map, we store the byte offset of the first flag
in a flag package in a flag value file. In flag.map, we store the within
package flag byte offset. Once we know the total offset, we can locate
the flag in the flag value file. However, this offset may not work for
flag info file. Currently we only have boolean flags. Each boolean flag
value and info takes up 1 byte in flag value and flag info file. So the
byte offsets are the same. But in the future, when we add a new flag
value type, or add more contents to flag info file. Then the byte offset
for flag value file and flag info file may not be same.
Instead, we should store index rather than offset. The package map
should store the index of the first flag in this package. The flag map
stores the within package index. Then flag value read api and flag info
read api can then infer the byte offset independently.
Bug: b/321077378
Test: atest -c
Change-Id: Iad89776d5369715ba2d8faaea18261ac3271f13b
`PRODUCT_MODULE_BUILD_FROM_SOURCE` has been added explicitly to the
products that have `HOST_CROSS_ARCH=arm64`, so we do not need this
special case here anymore.
Bug: 308188056
Test: presubmits
Change-Id: Ide3dbf9c3674683f2e0546403622cf6b8fe78739
For GRF devices, the system partition might be shared between different
products using different kernels. Hence putting the 16K boot option OTA
on system partition would not work for such project.
Test: th
Bug: 293313353
Bug: 328166454
Bug: 329808458
Change-Id: I2ba3ad4f28f3569c6b8e275849988328f9d73552
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
We currently do not have many products that cross compile to
linux_bionic, and none of them use google apexes.
One exception is `mainline_sdk` product, but this product exclusively
builds using the `mainline` release config. This release config contains
the necessary RELEASE_APEX_CONTRIBUTIONS_* to provide sources during the
build, so we do not need this additional special-case here
Bug: 308188056
Test: lunch trout_arm64-next-userdebug && get_build_var
PRODUCT_PACKAGES; verified that google apexes do not appear there before
this CL, effectively making this CL a no-op for that product
Change-Id: Ibfdc742b6ae01242be22a3d3f6bb3c0cf551705f
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
`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
